View Issue Details

IDProjectCategoryView StatusLast Update
0004712ardourbugspublic2020-04-19 20:16
Reporterahellquist Assigned Tocth103  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Target Version3.0 
Summary0004712: Enabling monintor for an existing session works but disabling it crashes Ardour (Arduor3 Beta 3)
DescriptionEnabling monintor for an existing session works but disabling it crashes Ardour (Arduor3 Beta 3)

Not much more to add
TagsNo tags attached.

Relationships

duplicate of 0004781 closedcth103 Session properties ( Cheched use monitor this session) Gui failed went gray all windows had to kill session. 

Activities

ahellquist

2012-02-11 22:53

reporter   ~0012785

xbuntu 64bit 11.10
3.0.0.15 Stock kernel

ahellquist

2012-02-12 02:21

reporter   ~0012786

By enabling I mean checking the checkbox at:

Session -> Properties -> Monitorin -> Use monitor section in this session

ahellquist

2012-02-12 10:55

reporter   ~0012787

Crash is really a hanging and there is nothing showing up in console.
I can switch between the mixer and other views but they are not responding to input.


If there was sound playing during the switch, the system get stuck outputting a random frequecy until i let the windowmanager kill the app or close it with ctrl-c in console.

cth103

2012-03-24 23:04

administrator   ~0013025

Any chance you could run Ardour in gdb, and when it hangs do a Ctrl-Z in the console and attach the output of

thread apply all bt

?

ahellquist

2012-03-24 23:19

reporter   ~0013030

Will do a gdb

2012-03-25 19:25

 

0004712.backtrace (33,491 bytes)

ahellquist

2012-03-25 19:26

reporter   ~0013033

Backtrace uploaded. I hope I did manage because this was my first bt

cth103

2012-03-25 20:31

administrator   ~0013034

Perfect. Should be fixed in SVN 11760.

ahellquist

2012-03-25 20:49

reporter   ~0013037

Nice !

system

2020-04-19 20:16

developer   ~0022965

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2012-02-11 22:51 ahellquist New Issue
2012-02-11 22:53 ahellquist Note Added: 0012785
2012-02-12 02:21 ahellquist Note Added: 0012786
2012-02-12 10:55 ahellquist Note Added: 0012787
2012-03-24 23:04 cth103 Note Added: 0013025
2012-03-24 23:04 cth103 Status new => feedback
2012-03-24 23:06 cth103 Relationship added duplicate of 0004781
2012-03-24 23:09 cth103 cost => 0.00
2012-03-24 23:09 cth103 Target Version => 3.0 beta4
2012-03-24 23:19 ahellquist Note Added: 0013030
2012-03-25 19:25 ahellquist File Added: 0004712.backtrace
2012-03-25 19:26 ahellquist Note Added: 0013033
2012-03-25 20:31 cth103 Note Added: 0013034
2012-03-25 20:31 cth103 Status feedback => resolved
2012-03-25 20:31 cth103 Resolution open => fixed
2012-03-25 20:31 cth103 Assigned To => cth103
2012-03-25 20:49 ahellquist Note Added: 0013037
2012-05-23 15:08 cth103 Target Version 3.0 beta4 => 3.0
2020-04-19 20:16 system Note Added: 0022965
2020-04-19 20:16 system Status resolved => closed