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.
Build: NetBeans IDE Dev (Build 100518-b38c840a1311) VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02 OS: SunOS Stacktrace: java.lang.NullPointerException at org.netbeans.modules.progress.ui.StatusLineComponent.processSelectedProgressEvent(StatusLineComponent.java:341) at org.netbeans.modules.progress.spi.Controller.runNow(Controller.java:334) at org.netbeans.modules.progress.spi.Controller$1.actionPerformed(Controller.java:93) at javax.swing.Timer.fireActionPerformed(Timer.java:271) at javax.swing.Timer$DoPostEvent.run(Timer.java:201) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
Created attachment 99125 [details] stacktrace
Created attachment 99126 [details] stacktrace
Regression from your patch, very probably :-( Looking at it...
Created attachment 99132 [details] stacktrace Going back to IDE from another app.
Yep - if you have some at least semi-reproducible steps, that would be useful, thanks.
Changeset: 310c73829b9f Author: Dafe Simonek <dsimonek@netbeans.org> Date: 2010-05-18 16:03 Message: #186290: bar may not be initiated now because of different policy for suspended tasks Issue #186290 - NullPointerException at org.netbeans.modules.progress.ui.StatusLineComponent.processSelectedProgressEvent
not fixed, see exception report 389927
the fix just didn't make it to the daily build yet - it's our wonderful build system :-(
I have set 310c73829b9f in my build
I see, it seems variable label may be null while variable bar is non-null. However, I made another patch 31e1f5bb3cc1 (correct bug fix 184430) so this bug should be obsolete, as StatusLineComponent code was returned to the old state. Sorry for troubles.
I see the issue in build netbeans-trunk-nightly-201005182201-javafx-windows.exe
I saw this issue in build 201005182201 java.lang.NullPointerException at org.netbeans.modules.progress.ui.StatusLineComponent.processSelectedProgressEvent(StatusLineComponent.java:344) at org.netbeans.modules.progress.spi.Controller.runNow(Controller.java:337) at org.netbeans.modules.progress.spi.Controller$1.actionPerformed(Controller.java:96) at javax.swing.Timer.fireActionPerformed(Timer.java:271) [catch] at javax.swing.Timer$DoPostEvent.run(Timer.java:201) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:137) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Integrated into 'main-golden', will be available in build *201005192201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/310c73829b9f User: Dafe Simonek <dsimonek@netbeans.org> Log: #186290: bar may not be initiated now because of different policy for suspended tasks Issue #186290 - NullPointerException at org.netbeans.modules.progress.ui.StatusLineComponent.processSelectedProgressEvent
Created attachment 99231 [details] stacktrace trigger svn update for 8 projects
Created attachment 99236 [details] stacktrace
Created attachment 99240 [details] stacktrace
Created attachment 99253 [details] stacktrace
Created attachment 99261 [details] stacktrace
Created attachment 99309 [details] stacktrace
What is the status of this issue ? (6.9 hr fix candidates must be P1)
Hi, status of this bug is as a stated a few days ago (in this issue comment): ---- I made another patch 31e1f5bb3cc1 (correct bug fix 184430) so this bug should be obsolete, as StatusLineComponent code was returned to the old state. ---- So this bug is fixed and doesn't affect the trunk not release69 build, as bugfix of 184430 was propagated into release69 as well. Cheers.
Just to make the story complete, issue was reopened by javydreamercsw who saw this issue on May 18 build. That's true, but issue was fixed next day by me and javydreamercsw probably overlooked my fix.
Issue was also reported by NetCAT participants (javydreamercsw, ingoreinhart, hmichel) hence adding [69cat] prefix.
Thanks for explanation David. I added 69_HR_FIX keyword - to verify that it's already fixed in NB 6.9 during HR.
no further duplicate, marking as verified.
*** Bug 188496 has been marked as a duplicate of this bug. ***