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 200707221200) VM: Java HotSpot(TM) Client VM, 1.5.0_06-b05 OS: Windows 2000, 5.0, x86 User Comments:
Created attachment 45865 [details] stacktrace
oh, well. Not sure we can do something about an automated OOME report without further details
Reporter, can you provide more informations, like what did you do when you get OOME, attach dump..? Please, look on page http://wiki.netbeans.org/wiki/view/FaqNetBeansAndOOMEJa
I'm for to either not report OOME automatically or report it to special component in "ide" subcomponent.
Build: NetBeans IDE Dev (Build 200708040000) VM: Java HotSpot(TM) Client VM, 1.5.0_12-111 OS: Mac OS X, 10.5, i386 User Comments:
Created attachment 46166 [details] stacktrace
Build: NetBeans IDE Dev (Build 070805) VM: Java HotSpot(TM) Client VM, 1.5.0_12-b04 OS: Windows XP, 5.1, x86 User Comments: Steps: 1. Invoke "CVS | Checkout" wizard 2. Enter CVSRoot :pserver:anonymous@cvs.dev.java.net:/cvs 3. In 2nd step of checkout wizard enter module: "genesis" 4. Checkout
Created attachment 46188 [details] stacktrace
Could you please describe "further details" you want to get from me? If I'm able to solve the issue, I'd solve and just report the solution. Neverthless I guess that the nb console consumed to much memory :)) .. what additional info could I have? I just run application producing very lot of logging information into std output, I it should be clear from problem description. That's all. (If I would be on your place, I would suggest, that to much log was produced "in batch" (from nb view), so the nb output console buffer didn't reserve enough memory. When I running the same application not from NB, problem never occurs, when from NB, time to time the same outOfMemory..) Regards
Well, by details I mean stuff like. 1. what you did before the error occurs, possibly with reproducible steps. 2. more details about your machine. How much memory it has etc. 3. details about the amount of output. when I've previously done fixes in the output window performance, it scaled quite well and I was able to spit out and browse more output than I had physical memory. (1 GB on macosx). Note that the OOME comes from java NIO which does direct memory buffering of parts of the output file.
Better to try english version - http://wiki.netbeans.org/wiki/view/FaqNetBeansAndOOME Generally IDE redirects output to a file and maps it into memory as a ByteBuffer. If the file the so large that the JVM cannot allocate address space for it OOME is thrown. Do you have an estimation how big output is created (Milos: where are these files stored?) Since this is very special OOME we can think about some special cases to handle this and recover even if it would mean that we stop to process output and give notification that it is too large now.
System.getProperty("java.io.tmpdir") which points to your temp directory (varies with OS)
Build: NetBeans IDE Dev (Build 200708170000) VM: Java HotSpot(TM) Client VM, 1.5.0_12-b04 OS: Windows XP, 5.1, x86 User Comments: doing nothing, just sitting idle and got this error. There's a mix of a dozen or so rhtml and rb files open.
Created attachment 46812 [details] stacktrace
Build: NetBeans IDE Dev (Build 200708200000) VM: Java HotSpot(TM) Client VM, 1.5.0_10-b03 OS: Windows XP, 5.1, x86 User Comments:
Created attachment 47202 [details] stacktrace
possibly a duplicate of #90267
duplicate of #90267 *** This issue has been marked as a duplicate of 90267 ***