[ardour-dev] Some problems with Ardour 2.0 beta 10 on OSX

[Stéphane Letz]

Hi all,

Nice work (-: , but i get some problems with Ardour 2.0 beta 10 on OSX:

1) when adding/removing tracks, quitting the session does not show  
the "Save session" dialog although the state is then correctly saved.

2) when running under jackdmp I sometimes get the following crash  
when quitting:

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x0000000c

Thread 0 Crashed:
0   libjack.0.dylib               	0x02cd441d Jack::GetGraphManager()  
+ 23 (JackLibClient.cpp:32)
1   libjack.0.dylib               	0x02cd26ff WaitGraphChange() + 17  
(JackAPI.cpp:210)
2   libjack.0.dylib               	0x02cd3a09  
jack_port_get_connections + 51 (JackAPI.cpp:643)

Thread 1:
0   libSystem.B.dylib             	0x90024427  
semaphore_wait_signal_trap + 7

Thread 2:
0   libSystem.B.dylib             	0x90009857 mach_msg_trap + 7
1   com.apple.audio.midi.CoreMIDI 	0x9663693b  
XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
2   com.apple.audio.midi.CoreMIDI 	0x9662ee8d MIDIInPortThread::Run()  
+ 113
3   com.apple.audio.midi.CoreMIDI 	0x9662fb6d XThread::RunHelper 
(void*) + 17
4   com.apple.audio.midi.CoreMIDI 	0x966374ad CAPThread::Entry 
(CAPThread*) + 93
5   libSystem.B.dylib             	0x90023d87 _pthread_body + 84

Thread 3:
0   libSystem.B.dylib             	0x900bc8bc poll + 12

Thread 4:
0   libSystem.B.dylib             	0x900bc8bc poll + 12
1   <<00000000>> 	0x039107b0 0 + 59836336

Thread 5:
0   libSystem.B.dylib             	0x900bc8bc poll + 12

Thread 0 crashed with X86 Thread State (32-bit):
   eax: 0x00000004    ebx: 0x02cd4412 ecx: 0x00000000 edx: 0x039f6100
   edi: 0x00000001    esi: 0x00000006 ebp: 0xbfffd388 esp: 0xbfffd370
    ss: 0x0000001f    efl: 0x00010202 eip: 0x02cd441d  cs: 0x00000017
    ds: 0x0000001f     es: 0x0000001f  fs: 0x00000000  gs: 0x00000037

The crash actually happens in an assert that test if  the global  
context is correct. I'm almost sure the jack client get released then  
*later* on  the jack_port_get_connections function get called. Could  
it be a consequence of the "stop AudioEngine (JACK client) at  
shutdown, as first step, not last" change?

3) when adding audio using the "Session/Add existing audio / to  
track"; i select an audio file, if the audio file is not loadable for  
any reason, the "Error : cannot open input sound file XXX" message is  
displayed and the close button does not work =>  I have to kill Ardour.

Stephane