Bug 83370 - Eclipse compiler problem
Summary: Eclipse compiler problem
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.1 RC2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-01-21 03:04 EST by Carlo Marchiori CLA
Modified: 2009-08-30 02:05 EDT (History)
0 users

See Also:

Attachments
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 Carlo Marchiori CLA 2005-01-21 03:04:51 EST 
The problem is described at http://issues.apache.org/jira/browse/XALANJ-2046.
I have no time to copy everything here. 

Under heavy load and it seems that ibm jvm heap (version 1.4.1) gets corrupted 
and either a heap dump or strange exceptions showing that heap memory is 
corrupted happen. 

This happens only when xalan is compiled with Eclipse compiler. It never happen 
when compiled with Sun compiler. 

In the xalan pages, you can find code to test the bug on appropriate machines.

Carlo.
Comment 1 Carlo Marchiori CLA 2005-01-21 03:07:15 EST 
It may be a bug of ibm jvm since the problems arises in my opinion when the 
code is compiled into machine code, not at the first execution.

Besides jvm verifier should reject code that can harm jvm heap.

Carlo.
Comment 2 Olivier Thomann CLA 2005-01-21 11:41:29 EST 
I think this is a JIT bug. The Eclipse compiler might produced a slightly
different bytecode and the JIT gets confused.
I would try it with a newer VM.
Comment 3 Philipe Mulet CLA 2005-04-07 09:53:43 EDT 
Please reopen if you can reproduce using a different vendor VM.
Comment 4 Frederic Fusier CLA 2005-06-08 06:01:48 EDT 
Close at there's near 5 months without any feedback on this issue
=> consider it does no longer happen
Comment 5 Denis Roy CLA 2009-08-30 02:05:49 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.