165374 – profiling MemoryClass from automation framework periodically crashes the JVM

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 165374 - profiling MemoryClass from automation framework periodically crashes the JVM

Summary: profiling MemoryClass from automation framework periodically crashes the JVM

Status:	CLOSED DUPLICATE of bug 164378

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	TPTP (show other bugs)
Version:	unspecified
Hardware:	Other Windows Server 2003

Importance:	P3 critical (vote)
Target Milestone:	---
Assignee:	Karla Callaghan
QA Contact:

URL:
Whiteboard:	closed471
Keywords:

Depends on:
Blocks:

Reported:	2006-11-21 16:06 EST by Alan Haggarty
Modified:	2016-05-05 10:51 EDT (History)
CC List:	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 Alan Haggarty

2006-11-21 16:06:12 EST

Found in:
TPTP-4.3.0-200611070100 and
TPTP-4.3.0-200611160100A

Platform:Windows 2003 SP1 server on EM64T

Steps to reproduce:

Test class:
HEAD/test-results/platform/org.eclipse.tptp.ac.testautomation/automation-files/external_classes/MemoryClass.java

1. Profile MemoryClass by selecting Basic Memory Analysis as the
profiling option. 
2. Press enter until the program terminates.

repeat these two steps until RAServer crashes due to JVM crash ie:
D:\haggarty\11070100\ac430i3\bin>RAServer.exe
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000001f81da1, pid=1916, t
id=2568
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C  [hcclsm.dll+0x1da1]
#
# An error report file with more information is saved as hs_err_pid1916.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

If you open the statistics you can see the data was succesfully collected before
the crash.

Comment 1 Karla Callaghan

2006-11-21 19:54:57 EST

This is a duplicate - same error seen on Win EM64T reported in bug 164378.

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

Comment 2 Valentina Popescu

2007-05-29 00:47:12 EDT

Updated target to match the iteration when this defect was processed

Comment 3 Kathy Chan

2010-11-18 18:48:58 EST

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.