View Issue Details

IDProjectCategoryView StatusLast Update
0004454ardourbugspublic2012-05-23 15:08
Reporteracolomb Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status acknowledgedResolutionopen 
Target Version3.0 
Summary0004454: Renaming track misses some ports
Description1. Show the MIDI connection manager
2. Create a MIDI track named "MIDI"
3. In the MIDI connection manager, right-click the "MIDI out" field and add an audio port.
4. Rename the track to "MIDI A"
5. Notice how the MIDI input is correctly renamed to "MIDI A in" in the connection manager, but the output is still called "MIDI out"
6. In the Log window, the following error message appears:

[ERROR]: JACK: Unknown destination port port_name = ardour:MIDI/midi_out 1
Additional InformationIt seems to be a problem only with the display and internal data structure of the connection manager, the session is saved correctly and e.g. patchage shows the renamed ports.

I've had some similar issues also with Audio tracks, there is probably a more general bug in the connection handling.
TagsNo tags attached.

Activities

acolomb

2011-11-07 11:13

reporter   ~0011925

Right after reporting this issue, I saved and closed the session with the MIDI connection manager still open. While closing the session, A3 aborted with this message:
ardour-3.0: /usr/include/boost/smart_ptr/shared_ptr.hpp:418: T* boost::shared_ptr<T>::operator->() const [with T = const PortGroup]: Assertion `px != 0' failed.
Aborted
Is this related or should I try to reproduce and create a separate issue?

cth103

2011-11-08 02:11

administrator   ~0011938

The first bug should be fixed in SVN 10490. Can you still reproduce the abort?

2011-11-08 09:48

 

acolomb

2011-11-08 10:44

reporter   ~0011942

Reproduced in SVN r10474 and created a backtrace for the abort().

acolomb

2011-11-08 10:51

reporter   ~0011943

Last edited: 2011-11-08 11:38

I could not reproduce the abort() on session close with current SVN r10491. There were a few other problems, though:
1. First time I tried to reproduce the above error, it aborted already when adding a new MIDI track with the MIDI connection manager window visible. Unfortunately I didn't get a backtrace of that one and have been unable to reproduce it so far. EDIT: Later I got the same abort() message (as far as I remember) much later in the process... may have to do with #2 below. Backtrace attached as "backtrace-bug4454-a3-six.txt".
EDIT2: This problem seems to appear randomly, next time I tried it aborted before even adding a track, while hovering over the MIDI connection manager window. Backtrace available, but I don't want this report to grow out of proportion :-)

2. On the second try, I noticed a rendering error after adding an audio output (see Step 3 above). The MIDI connection manager incorrectly highlighted the MIDI port, see attached screenshot.

3. The next time, while still trying to reproduce any of the abort()s, I could add the MIDI channels, but only the first one appeared in the connection manager. See attached screenshot #2.

2011-11-08 10:51

 

bug4454-wrong-border.png (24,205 bytes)   

2011-11-08 10:51

 

bug4454-missing-tracks.png (188,743 bytes)   

2011-11-08 11:33

 

backtrace-bug4454-a3-six.txt (23,428 bytes)   

cth103

2011-11-08 14:15

administrator   ~0011949

Things should be a bit better in SVN 10494; would you mind giving it another test?

acolomb

2011-11-08 15:16

reporter   ~0011952

I could not exactly reproduce the abort - seems fixed.

After starting out with a new session and trying various steps from the original report multiple times and in random order, I saved the session and Ardour froze up while closing it. I have no clue if this is related, but attaching the backtrace (after interrupting) anyway.

2011-11-08 15:16

 

paul

2011-11-09 11:08

administrator   ~0011957

the freeze is apparently caused by the audioengine/the JACK RT-audio thread being blocked waiting for a process cycle to complete. the GUI is waiting for the engine to signal that the session is no longer connected to it, which won't happen until the current process cycle is over. its not clear why it gets stuck.

cth103

2011-11-14 17:02

administrator   ~0012012

acolomb: can you reproduce the hang on close?

acolomb

2011-11-22 00:26

reporter   ~0012175

Not exactly the hang--but a segmentation fault. I can't really judge if it is related or maybe caused by some other bug, but it happened while closing the same session that froze up last time. Attaching backtrace.

2011-11-22 00:26

 

cth103

2011-11-22 00:35

administrator   ~0012176

Last edited: 2011-11-22 00:36

OK, that's just a common-or-garden sort-of-race during session deletion; thanks.

acolomb

2011-11-22 00:54

reporter   ~0012178

Okay, here is another SIGABRT backtrace which looks similar to the first one. This is r10744 by the way.

2011-11-22 00:54

 

Issue History

Date Modified Username Field Change
2011-11-07 11:11 acolomb New Issue
2011-11-07 11:13 acolomb Note Added: 0011925
2011-11-07 14:34 cth103 cost => 0.00
2011-11-07 14:34 cth103 Target Version => 3.0-beta1
2011-11-08 02:11 cth103 Note Added: 0011938
2011-11-08 02:11 cth103 Status new => feedback
2011-11-08 09:48 acolomb File Added: backtrace-bug4454-abort.r10474.txt
2011-11-08 10:44 acolomb Note Added: 0011942
2011-11-08 10:51 acolomb Note Added: 0011943
2011-11-08 10:51 acolomb File Added: bug4454-wrong-border.png
2011-11-08 10:51 acolomb File Added: bug4454-missing-tracks.png
2011-11-08 11:33 acolomb Note Edited: 0011943
2011-11-08 11:33 acolomb File Added: backtrace-bug4454-a3-six.txt
2011-11-08 11:38 acolomb Note Edited: 0011943
2011-11-08 14:15 cth103 Note Added: 0011949
2011-11-08 15:16 acolomb Note Added: 0011952
2011-11-08 15:16 acolomb File Added: backtrace-bug4454-a3-eight_freeze.txt
2011-11-09 11:08 paul Note Added: 0011957
2011-11-14 17:02 cth103 Note Added: 0012012
2011-11-15 15:46 cth103 Target Version 3.0-beta1 => 3.0-beta2
2011-11-22 00:26 acolomb Note Added: 0012175
2011-11-22 00:26 acolomb File Added: backtrace-bug4454-a3-eight_segfault.txt
2011-11-22 00:35 cth103 Note Added: 0012176
2011-11-22 00:36 cth103 Note Edited: 0012176
2011-11-22 00:54 acolomb Note Added: 0012178
2011-11-22 00:54 acolomb File Added: backtrace-bug4454-a3-nine_abort.txt
2012-01-10 20:46 cth103 Target Version 3.0-beta2 => 3.0-beta3
2012-02-14 17:20 paul Target Version 3.0-beta3 => 3.0 beta4
2012-04-23 22:03 cth103 Status feedback => acknowledged
2012-05-23 15:08 cth103 Target Version 3.0 beta4 => 3.0