Bug 511441 - SWTException below NewsUrlHandler$1.run (thrown in WebKit.evaluate)
Summary: SWTException below NewsUrlHandler$1.run (thrown in WebKit.evaluate)
Status: NEW
Alias: None
Product: MPC
Classification: Technology
Component: Install (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5.4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-01 04:48 EST by EPP Error Reports CLA
Modified: 2017-02-01 05:08 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2017-02-01 04:48:08 EST 
The following problem was reported via the automated error reporting:

Message: Unhandled event loop exception
org.eclipse.swt.SWTException: An exception was raised in JavaScript
    at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:970)
    at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:395)
    at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
    at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
    at org.eclipse.epp.internal.mpc.ui.wizards.NewsUrlHandler$1.run(NewsUrlHandler.java:71)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4475)



Bundles:
| org.eclipse.epp.mpc.ui | 1.5.2.v20161005-1414 | 1.5.2.v20161005-1414 |
| org.eclipse.swt | 3.106.0.v20161207-1901 | 3.106.0.v20161207-1901 |

Operating Systems:
| Linux | 4.8.0 | 4.8.15.fc25 |


The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5860f2b5e4b0552b1cfec959 for the latest data.

Thank you for your assistance.
 Your friendly error-reports-inbox.


Created on behalf of reckord@xxxxxx.xxx
Comment 1 Carsten Reckord CLA 2017-02-01 05:08:13 EST 
We should probably wrap the Javascript into an anonymous function to avoid conflicts with the page Javascript's namespaces.

Also, the JS call should handle this exception.