JVM Crash on trigger OSX 10.6.8 latest Java - Bome Forums Archive 2005

arstrand

2012-04-01 07:46:27

I upgraded to the latest OSX 10.6.8 from 10.6.6 to try and get your software to work. I also upgraded to to the latest Java. Unfortunate the incoming triggers cause a total failure. Only thing I can do now is remove the software and try something else. Bahhumbug. I was really looking forward to purchasing this for a gig next weekend.

java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-10M3527)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode)
Allen-Strands-MacBook-Pro:~ astrand$

I go to Midi input filter with midi message selected and try to enter 9037 (note on for note 37) I get 903 entered and the the JVM crashes. Please advise if you have a patch that will fix this.

Code: Select all

Process:         JavaApplicationStub [438]
Path:            /Applications/Bome's Midi Translator Pro.app/Contents/MacOS/MidiTranslatorPro
Identifier:      com.bome.miditranslator.pro
Version:         1.7.2 (511)
Code Type:       X86 (Native)
Parent Process:  launchd [107]

Date/Time:       2012-03-31 22:42:18.414 -0700
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          5677 sec
Crashes Since Last Report:           2
Per-App Interval Since Last Report:  718 sec
Per-App Crashes Since Last Report:   2
Anonymous UUID:                      3C74D776-5E80-48ED-92C8-759857127FF4

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread:  22
(...)
Thread 22 Crashed:
0   libmt.so                      	0x2863a0ab Tr::TTransMidiAction::matches(Tr::TIncomingActionParams&) + 323
1   libmt.so                      	0x2868b2b5 Tr::TTransMsg::Matches(Tr::TIncomingActionParams&, int volatile&) + 57
2   libmt.so                      	0x2867f85b Tr::TTransEngine::DoTranslations(Tr::TIncomingActionParams&, int volatile&, Tr::TTransList*, Tr::_TOutgoingActionParams&) + 185
3   libmt.so                      	0x2867fa50 Tr::TTransEngine::HandleIncomingAction(Tr::TIncomingActionParams&, int volatile&) + 226
4   libmt.so                      	0x2867fb8c Tr::TTransEngine::HandleMidiInput(int, unsigned char*, int, Tr::TExecuteContext, int&) + 154
5   libmt.so                      	0x2867ebe5 Tr::TTransEngine::OnMidiMessage(int, unsigned long long, unsigned char*, int, int&) + 53
6   libmt.so                      	0x286626c9 Tr::MidiManager::OnMidiDeviceMessage(Tr::TMidiInputBase*, unsigned long long, unsigned char*, int) + 251
7   libmt.so                      	0x286aa3e6 Tr::TMidiInputBase::SplitAndDispatchMidiMessage(unsigned long long, unsigned char*, int) + 216
8   libmt.so                      	0x286acae7 Tr::TMidiInputMac::_midiReadProc(MIDIPacketList const*, void*, void*) + 69
9   com.apple.audio.midi.CoreMIDI 	0x28b3d9f3 MIDIProcess::RunMIDIInThread() + 271
10  com.apple.audio.midi.CoreMIDI 	0x28b202d9 XThread::RunHelper(void*) + 17
11  com.apple.audio.midi.CoreMIDI 	0x28b1fca6 CAPThread::Entry(CAPThread*) + 96
12  libSystem.B.dylib             	0x94e4a259 _pthread_start + 345
13  libSystem.B.dylib             	0x94e4a0de thread_start + 34
(...)

florian

2012-04-12 11:50:19

Hi,

thanks for the bug report (sorry for the late response). This seems to be a bug in MT.
Apparently it happens when MT is processing MIDI data while entering a translator. That should work normally, but here it crashed.

I guess you can work around it by closing the MIDI devices (or hit Panic), enter the translator's MIDI message, and then reactivate MIDI again.

We'll fix this for the next version.

Regards,
Florian

wilcofan

2014-09-08 17:08:01

I was entering a Midi Message in OSX 10.6.8 last night. Incoming tab.
There is a feature in the Mac version where an invalid message is warned, on the fly. (It's a bit annoying, BTW)
Mine crashed, while I was modifying the message. I hit backspace, then the new number, crash.

A workaround: instead of hitting backspace to remove a character, highlight it, and enter the new character.
It doesn't seem to trigger the error detection. I get no "invalid Midi message" popup. And seems to be fine.