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 187013 - [69cat] [ide] RC1 OOME when running ruby process for extended period
Summary: [69cat] [ide] RC1 OOME when running ruby process for extended period
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 03:29 UTC by esmithbss
Modified: 2013-05-17 15:32 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Messages file (507.69 KB, text/x-log)
2010-06-01 03:32 UTC, esmithbss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-06-01 03:29:32 UTC
[ BUILD # : 6.9 RC1 ]
[ JDK VERSION : 1.6.20 ]

While running an extended time test of a RoR rails app, RC1 generated an OOME
exception.
Comment 1 esmithbss 2010-06-01 03:32:53 UTC
Created attachment 99692 [details]
Messages file
Comment 2 esmithbss 2010-06-01 03:41:25 UTC
Heapdump is available from Burning Sun Enterprises at: http://www.burningsunenterprises.com/index.php?q=node/4
Comment 3 esmithbss 2010-06-01 03:48:09 UTC
Heapdump download also available via:

http://www.burningsunenterprises.com/uploads/187013-heapdump.hprof.tbz2
Comment 4 Peter Pis 2010-06-01 07:07:27 UTC
Reassigning for further evaluation.
Comment 5 Erno Mononen 2010-06-01 07:48:01 UTC
From what I can tell from the heap dump it seems that the output window is holding onto a large number of lines - I guess all the lines that the app you ran from the IDE printed. Clearing the OW window should help, but probably the OW should have some kind of a line limit.
Comment 6 Martin Entlicher 2011-02-09 14:59:16 UTC
Yes, Output Window simply does not scale.
Comment 7 Jaroslav Havlin 2013-05-17 15:32:56 UTC
This should be solved by fix of bug 185462.
Thank you for reporting.