Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 205635 - profiled java.exe under the component test crashs with heap allocation failure
Summary: profiled java.exe under the component test crashs with heap allocation failure
Status: CLOSED DUPLICATE of bug 138736
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jerome Gout CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-06 09:02 EDT by jkubasta CLA
Modified: 2016-05-05 11:06 EDT (History)
1 user (show)

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 jkubasta CLA 2007-10-06 09:02:12 EDT 
JVM v1.4.2
Windows XP + SP2

[Steps to reproduce] 
1.Create Component Test Project based on a simple Java program such as HelloWorld.java.
2.Jump to "Test" perspective
3.Set cursor onto the lowest node under Test Suite folder of the newly created test component project.
4.Execute [Profile]->[ComponentTest]
5.a windows pops up redirecting to "Profile and logging" perspective
6.java.exe unexpected crash reported from windows kernel

When I open the debbugger and check the failure point, the error was reported from heap-related function.
Comment 1 Paul Slauenwhite CLA 2007-10-09 09:36:32 EDT 
Profiling test suites is not a supported use case (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=75029).

Using 4.4.0.3, when the user attempts to profile a test suite, the following error message is displayed in the Test Launch Configuration dialog:

IWAT4029E No Test selected.

However, no tests appear to be selected.  Reopening 138736 to address in 4.5.

*** This bug has been marked as a duplicate of bug 138736 ***
Comment 2 Paul Slauenwhite CLA 2008-06-27 08:52:52 EDT 
Closing by default since not closed by the originator in the 7+ months since being resolved.  

Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.