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 49009 - [40cat] OutOfMemoryError when opening large jar in favorites tab
Summary: [40cat] OutOfMemoryError when opening large jar in favorites tab
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All Mac OS X
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-09-14 15:05 UTC by Unknown
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump of OutOfMemoryError (5.05 KB, text/plain)
2004-09-14 15:05 UTC, Unknown 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2004-09-14 15:05:19 UTC 
I get an OutOfMemoryError when opening a large jar file (13 
megabyte) in the Favorites tab.  See attachment for thread 
dump.
Comment 1 Unknown 2004-09-14 15:05:59 UTC 
Created attachment 17625 [details]
Thread dump of OutOfMemoryError
Comment 2 _ rkubacki 2004-09-23 07:54:48 UTC 
Thrown during icon resolving performed by Java support. BTW: What
library is distributed as a 13MB jar file? Also can you give us
details about IDE build, JDK, platform your configuration?
Comment 3 Martin Matula 2004-10-07 08:37:08 UTC 
I am unable to reproduce it. I tried it with rt.jar, opened several
packages. The memory (even the max heap size) does not go over 30MB.
If it still happens to you, please reopen and provide more info (build
number, how many packages/directories in the jar you expand).
Comment 4 Milan Kubec 2004-10-07 11:32:04 UTC 
If your unable to reproduce then resolve as worksforme and not fixed.
Comment 5 Milan Kubec 2004-10-07 11:32:37 UTC 
Better resolution.
Comment 6 Martin Matula 2004-10-07 11:46:00 UTC 
We've made a big amout of performance fixes expetially when it comes
to memory footprint. I guessed that thanks to these changes the
problem no longer occurs, that's why I originally marked the issue as
FIXED.
Comment 7 Jiri Kovalsky 2004-10-14 14:04:47 UTC 
This is NetCAT issue, updating summary accordingly.