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 114038 - OutOfMemory error in Profiler broke IDE
Summary: OutOfMemory error in Profiler broke IDE
Status: VERIFIED WONTFIX
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-28 17:25 UTC by Alexander Kouznetsov
Modified: 2007-08-29 12:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (1.73 MB, text/plain)
2007-08-28 17:27 UTC, Alexander Kouznetsov
Details
IDE output and threads dump (55.72 KB, text/plain)
2007-08-28 17:28 UTC, Alexander Kouznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-08-28 17:25:50 UTC
Product Version: NetBeans IDE Dev (Build 200708270000) 
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06 
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

Performed steps:
- Profiler was used to profile another instance of NetBeans (Memory Liveness with allocation stacks, each 50 object)
- At some take snapshot action OutOfMemoryError occurred and IDE became frozen for several minutes
- RESULT: After that it became responding and it was shown that memory usage lowered to 162 MB of 255 MB. However, even
Profiler VM Telemetry windows were updating, the rest of IDE became non working. Any profiler action just did nothing,
any other action in IDE also did nothing while user was able to open menus they just did nothing. Some actions like
zooming VM Telemetry were still working but no menu, no toolbar button, no shortcut were working. Invoked menu items
were shown as selected when the menus were opened again. User had to shutdown IDE.
Comment 1 Alexander Kouznetsov 2007-08-28 17:27:31 UTC
Created attachment 47642 [details]
messages.log
Comment 2 Alexander Kouznetsov 2007-08-28 17:28:10 UTC
Created attachment 47643 [details]
IDE output and threads dump
Comment 3 Tomas Hurka 2007-08-29 10:01:22 UTC
You cannot expect that the NetBeans will work correctly after exception is thrown. This is also case of this OOME - a lot of thing can go wrong, since NetBeans 
is heavily multithreaded application and OOME can be thrown in any place in any thread in NetBeans IDE. Closing as WONTFIX, since there is no way to fix this. 
You need to restart IDE and increase Xmx. 
Comment 4 Alexander Kouznetsov 2007-08-29 12:22:13 UTC
Verified