Bug 165225

Summary: Update manager fails using too much memory
Product: [Fedora] Fedora Reporter: Aaron Luchko <aaron>
Component: eclipseAssignee: Andrew Overholt <overholt>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: eclipse-bugs, tromey
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-03 16:17:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aaron Luchko 2005-08-05 16:43:05 UTC
Description of problem: While attempting to install plugins via the update
manager I recieved the warnings 

GC Warning: Repeated allocation of very large block (appr. size 16781312):
        May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 2101248):
        May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 9461760):
        May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 1052672):
        May lead to memory leak and poor performance.

and eventually eclipse exits with an out of memory error.

Version-Release number of selected component (if applicable):
eclipse-platform-3.1.0_fc-12

How reproducible:
Always

Steps to Reproduce:
1. Go to Find and Install in the update manager
2. Search for new features to install > Eclipse.org update site, Finish
3. Select EMF SDK 2.1.0 and go to install
  
Actual results:
Installation takes an extremely long time, the error warnings come up on the
command line, and eclipse eventually exits with an out of memory error.

Expected results:
All the stuff I just said, except not.

Comment 1 Tom Tromey 2005-08-09 16:48:11 UTC
One possible reason for this is that our http url handler
reads all the bytes of the remote resource into a byte[].
This can cause problems if the number of bytes is large.


Comment 2 Tom Tromey 2005-09-09 17:16:02 UTC
FYI, see this thread.
http://lists.gnu.org/archive/html/classpath/2005-09/msg00077.html


Comment 3 Andrew Overholt 2005-10-29 01:56:49 UTC
I just ran into this while attempting to install the EclipseDocs plugin
(http://eclipsedocs.berlios.de, I think).  I think the HTTP URL theory may be
valid 'cause with the Sun JVM I get progress as the plugin is downloading (ie.
8405 kB out of 16000 kB) but with gcj I get no progress and each jar just
finishes (or doesn't ;).

Updating subject.

Comment 4 Tom Tromey 2005-10-29 17:37:07 UTC
BTW, a patch for this problem went in to Classpath.
I'll try to get this into gcj.


Comment 5 Tom Tromey 2005-11-28 16:17:22 UTC
FYI -- this fix was brought in to the 4.1 tree by the classpath merge.


Comment 6 Tom Tromey 2006-01-21 01:02:32 UTC
I think this is fixed in rawhide.


Comment 7 Andrew Overholt 2006-02-03 16:17:10 UTC
Cool.  We can re-open if it rears its ugly head again.