This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | NullPointerException at org.netbeans.modules.java.hints.suggestions.NameAndPackagePanel$2$1$1.run | ||
---|---|---|---|
Product: | java | Reporter: | bb2eb |
Component: | Hints | Assignee: | Svata Dedic <sdedic> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | THREAD |
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 203682 |
Attachments: | stacktrace |
Description
bb2eb
2013-09-08 11:26:01 UTC
Created attachment 139798 [details]
stacktrace
I assume the fix "Create Subclass" was applied. The fix run from a RP, initializing an unsynchronized errorListener from a thread "A". Constructor spawns another task in a thread "B", which can execute immediately (in parallel to "A") and invoke the Runnable in RP. The Runnable COULD eventually run before "A" returns and sets up the Error Listener, though it does not seem likely. It's more probable that since errorListener variable is not synchronized and it is initialized from "A" thread, the EDT sees still a stale null value. Changed initialization / synchronization. Fixed in http://hg.netbeans.org/jet-main/rev/d79d04993cd0 Integrated into 'main-silver', will be available in build *201309150002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/d79d04993cd0 User: Svata Dedic <sdedic@netbeans.org> Log: #235652: ensured visibility of errorListener after initialization |