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.

Bug 213100 - Netbeans freezes, CPU at more than 100%, empty display
Summary: Netbeans freezes, CPU at more than 100%, empty display
Status: RESOLVED INCOMPLETE
Alias: None
Product: php
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.1.1
Hardware: PC Linux
: P2 normal (vote)
Assignee: Ondrej Brejla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-28 14:10 UTC by rogojine
Modified: 2012-05-28 15:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump using jstack (19.99 KB, application/octet-stream)
2012-05-28 14:10 UTC, rogojine
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rogojine 2012-05-28 14:10:54 UTC
Created attachment 119940 [details]
Thread dump using jstack

Netbeans wasn't active. I had switched to another virtual desktop. When I went back 20 minutes later, the Netbeans window was empty (only the window bar).

Unfortunately, I don't how to reproduce this bug. It just happened for the second time in a few months.
Comment 1 Ondrej Brejla 2012-05-28 14:17:27 UTC
Sorry, but I can't do anything with that thread dump...no php classes in there. If it consumes 100% cpu, try to make a profiling snapshot.

But there were a lot of performance improvments done for NB 7.2, so try 7.2 daily build [1]...it could be ok (and better than 7.2beta).

[1] http://bits.netbeans.org/download/trunk/nightly/latest/
Comment 2 rogojine 2012-05-28 15:34:10 UTC
I hoped maybe the thread dump could be useful, but it wasn't that important for me.

I don't think it should be called a "performance problem" though. When I saw NB freezing, I left it alone for at least half an hour, at more than 100% CPU load, and it still wasn't able to display the menu or the editor.

Anyway I've just installed NB 7.1.2. I'll try to update this ticket with a profiling snapshot if I ever encounter this bug again.
Comment 3 Ondrej Brejla 2012-05-28 15:36:17 UTC
Or as I wrote...try 7.2...dev builds...they are better than 7.1.2 afaik.