View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000595 | ardour | bugs | public | 2004-07-06 20:51 | 2008-11-20 23:39 |
| Reporter | Jeff | Assigned To | paul | ||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000595: Removing "master out" will result in crash | ||||
| Description | To reproduce: 1) Create new session 2) Remove "master out" buss 3) Add a new buss Ardour crashes. | ||||
| Additional Information | I'm testing beta 17.1 It appears that Ardour runs with the expectation of always having a valid master out buss (ARDOUR::Session::_master_out) Look at line 1482 of session.cc (Session::remove_route()). If &route == _master_out you're in trouble since _master_out becomes a dangling pointer after the route is deallocated. Adding the code after session.cc, line 1483: if (&route == _master_out) { _master_out = 0; } seems to fix the crash, but I'm not sure if that breaks the behavior that was intended. Are you supposed to be able to delete the master out? | ||||
| Tags | No tags attached. | ||||