This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 81 - Attached system crashes the JVM
Summary: Attached system crashes the JVM
Status: RESOLVED FIXED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: GUI (show other bugs)
Version: 3.4.3
Hardware: PC Linux
: P4 normal
Assignee: Gerd Behrmann
URL:
Depends on:
Blocks:
 
Reported: 2004-01-14 11:42 CET by Gerd Behrmann
Modified: 2006-03-19 17:59 CET (History)
2 users (show)

See Also:
Architecture:

Attachments
UPPAAL model triggering the problem. (16.67 KB, application/octet-stream)
2004-01-14 11:43 CET, Gerd Behrmann 		Details
Java Source file isolating the crash (905 bytes, text/plain)
2004-01-14 12:53 CET, Gerd Behrmann 		Details
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 Gerd Behrmann 2004-01-14 11:42:06 CET 
In the attached model, when switching to the Sampler template the JVM crashes.
Observed on both Windows and Linux.
Comment 1 Gerd Behrmann 2004-01-14 11:43:03 CET 
Created attachment 11 [details]
UPPAAL model triggering the problem.
Comment 2 Gerd Behrmann 2004-01-14 12:53:08 CET 
Created attachment 13 [details]
Java Source file isolating the crash
Comment 3 Gerd Behrmann 2004-01-14 12:53:55 CET 
It seems to be a JVM problem. I have created a small test program that can crash
the JVM (attached). I will submit this as a Java bug to Sun.
Comment 4 Gerd Behrmann 2004-01-14 13:46:46 CET 
Bug has been submitted to Java. They claim to have a three week response time
for reviewing the bug report. For the moment the workarround is to turn
antialiasing off when running Uppaal (only necessary if you happen to trigger
this bug).

I will leave this bug open until I get confirmation from Sun.
Comment 5 Gerd Behrmann 2004-06-10 13:20:03 CEST 
I still got no confirmation from Sun about this bug. I tried the new JRE 1.5
beta 2, but JVM still crashes. I will resubmit the bug when I have time.
Comment 6 Gerd Behrmann 2006-03-19 17:59:21 CET 
The problem seems to be resolved in Java 5 update 6.