JDK-4795377 : closing sequencer sometimes crashes the VM
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.sound
  • Affected Version: 1.4.2
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-12-18
  • Updated: 2003-12-17
  • Resolved: 2003-08-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
1.4.2_04 04Fixed
Related Reports
Relates :  
Relates :  

Name: bs26599			Date: 12/17/2002

Run the WTK/MMAPI midi tck test.
It will crash the VM.
WTK/MMAPI now has a workaround. The sequencer is not closed.

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D2AB850

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.

Current Java thread:
	at com.sun.media.sound.MixerThread.runNative(Native Method)
	at com.sun.media.sound.MixerThread.run(MixerThread.java:314)


###@###.### 2003-03-18:

When I run the following test program on 1.4.2beta, I get crashes - possibly related to this bug:

	<test program moved to bug 4835956>

###@###.### 2003-03-24
	Removed the test program. It did produce a crash, but at Sequencer.open() and not at close(). So I filed a new bug for it: 4835956, which is fixed and integrated for mantis-beta. 

	This bug here - crash at Sequencer.close() - remains not reproducible by me. I may have to install the WTK TCK to find out more.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_04 tiger FIXED IN: 1.4.2_04 tiger INTEGRATED IN: 1.4.2_04 tiger tiger-b17 VERIFIED IN: 1.4.2_04 tiger

EVALUATION ###@###.### 2002-12-17 Need to find out how to reproduce this bug. ###@###.### 2003-08-23 A long debug session led to a usable test case. The cause is the Audio Engine's non-thread safety: interactive MIDI events (inserted to a sequencer with MidiChannel's) can under certain conditions still be tried to be played after the sequencer object was closed (and the native object free'd), causing an ellgal access to the free'd memory. The fix consists in cleaning the queue from the sequencer's events (if any) before closing and freeing.

PUBLIC COMMENTS closing sequencer sometimes crashes the VM