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.
I have tried to set up Blackberry Development Using NetBeans Mobility steps: http://www.netbeans.org/kb/50/blackberry.html NetBeans crashed at step: 4. Use File tab of the Explorer and open build.xml of the project. Add this fragment of code right before the </project>: When I tried to edit build.xml NetBeans 5.0 beta 2 stopped responding and I had to shut it down. This problem reproduces all the time.
Hi, what exactly does it mean it "stopped responding"? Is the repainting of NetBeans dead? Is NetBeans grey? This would hint at a deadlock, can you please provide a thread dump and attach it to this issue? Also, can you please attach the IDE log file (messages.log under your user settings directory)? Thanks.
Created attachment 27741 [details] messages.log
stopped responding - meant NetBeans was grey messages.log is attached I do not know how to do a thead dump:( Recently I have tried again and everything was fine. The difference this time was that after starting NetBeans I have waited for about 15 minutes before creating mobile project. This could identify threading problem as you pointed out.
The problem is likely a race condition in XML editor/navigator. If you had the threaddump, I would be able to fix it otherwise I cannot do much. Please If you encounter the problem again then press Ctrl-BREAK (on Windows) or Ctrl-\ on linux in the console (you have to run NB with it) and the TD will be printed out. Other ways of getting TD (if you do not have console) are more complicated. On windows you need a special tool AFAIK, on linux kill -3 <PIDOF_NB> should work. I am downgrading the issue and marking as incomplete.
Created attachment 27751 [details] The is a threaddump showing a deadlock in XML editor/navigator from our qa-functional unit tests. Probably the same problem as the reporter's.
This is very likely a duplicate of Issue #70169. Both issues claims the deadlock happened when editing a build file. *** This issue has been marked as a duplicate of 70429 ***
Verified as duplicate of another issue. Thanks for your report anyway !