Bug 29104 - M4 Workbench appears to lock up after build
Summary: M4 Workbench appears to lock up after build
Status: RESOLVED DUPLICATE of bug 28228
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Linux-GTK
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-07 13:56 EST by Randal Cobb CLA
Modified: 2003-01-08 10:25 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Randal Cobb CLA 2003-01-07 13:56:26 EST
Since upgrading to M4, I have not been able to perform a 'Project...', 'build
all', or 'build project'.  What appears to happen is, the source files get
compiled correctly, then the gui appers to 'hang'.  CPU resources spike to 100%
utilization and the gui will no longer redraw/repaint regardless of how long you
let it run.  I've left it running over night and it was still locked up the next
morning.  I have noticed that the underlying JVM goes to 100% cpu utilization
and slowly consumes memory.  For example, at the point that the workbench
freezes, the JVM may only be consuming about 180Mb ram, but as time passes, the
consumption increases by about 1mb per minute up to a maximum of about 280Mb
ram.  I have tried to isolate the JVM by trying three different SDKs: IBM 1.3.1
sp3, Sun 1.3.1_06, and Sun 1.4.1.  All do exactly the same thing.

The only way to recover is to kill the Java thread that is consuming all the CPU
and memory resources, unfortunately, in doing so, I get no .log to review or
attach here.

My environment is as follows:  PIII-750Mhz, 512Mb ram, Slackware 8.1 w/ 2.4.20
kernel (backing up to 2.4.18 kernel revision proves fruitless), DropLine Gnome 2.0

I can easily reproduce this.
Comment 1 Tod Creasey CLA 2003-01-08 10:25:53 EST

*** This bug has been marked as a duplicate of 28228 ***