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.
NetBeans IDE Dev (Build 20080715153428) Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b13 System: Windows XP version 5.1 The debugger stops working after killing sessions an indeterminate number of times. I do not have a reproducible case, however, start with 1. a simple web project with embedded javascript with debugger keyword 2. only Toops option set is suspend on debugger 3. set client side debug project property only 4. start debug, wait for debugger to stop, with step icons lit 5. kill session 6. repeat 7. eventually the debugger will not stop on the keyword, the toolbar icons will be greyed except for stop and pause, and can only exit the session by IDE restart. This was also observed in testing the same project switching from Firefox client side project property to IE. The debug session will fail. I is just not happening consistently.
I have a scenario that reproduced the problem with yesterday and today's installer builds. Attaching 2 projects: debuggerforFF and debuggerforIE. 1. leave Tools options suspend on debugger keyword as default 2. set browser general option to firefox as default 3. open each project - only client side debugging should be set for appropriate browser 4. set debuggerforFF as main project and run debug (ctrl + F5) 5. project will suspend on debugger. 6. Kill session via toolbar icon 7. set debuggerforIE as main project and run debug 8. if project suspends on debugger, then press kill 9. repeat steps 4 - 8. Eventually the debug toolbar will be greyed and the Sessions window will show not connected while browser has the splashscreen loaded "Launching Netbeans ..". Need to reboot the machine to regain control.
Created attachment 65454 [details] project 1
Created attachment 65455 [details] project 2
Created attachment 65456 [details] log
This turns out to be IE specific issue in the scenario of 5 killed suspend on debugger sessions. Thanks to Deva who provided extra dlls and debuggers.
Updating the summary as this was found to be an mdm.exe hang issue, in some machine configurations generally after 5 debug sessions. However this is not limited to suspend operation. The workaround for the hang for now is to run taskmgr and kill mdm.exe process.
I have updated the summary once again after I was able to launch more than 40 client-side sessions today before an apparent hang -- I say apparent as I was beginning to see null debug sessions in a monitoring tool we use. The previous day I had experimented with disabling several IE add-ons in an attempt to isolate perhaps an offending one. After re-enabling all the add-ons that had been installed in my machine, debug sessions appear to have been improved. We are still working on this issue as we have seen this problem in some but not in all machines.
It seems that the root problem is caused by other extensions which gets loaded into IE process which doesn't do cleanup properly. If NetBeans extension is the only enabled add-on, we don't see any problem. It is harder to figure out what exactly other add-ons are doing. Instead of just showing the splash screen with a busy hour glass cursor, we have decided to show a dialog indicating the problem and appropriate actions necessary to continue further
*** Issue 144669 has been marked as a duplicate of this issue. ***
Dialog to inform the user about MDM state and the action they need to take is in place.