View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005113 | ardour | bugs | public | 2012-09-30 18:29 | 2012-09-30 20:05 |
| Reporter | nido | Assigned To | nido | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 beta5 | ||||
| Summary | 0005113: loading previously crashed project results in either freeze or crash | ||||
| Description | I was working on a project which has been used in ardour3-svn and ardour3 beta5. At one point, I disconnected jackd from the menu, and ardour exited. Now I'm left with a project which exhibits curious behaviour. When I open the project, it asks me whether to recover the crash data, or to ignore it. The option I choose here seems irrelevant. After trying to load it comes up with the following message: "unable to create port: failed constructor Click the Close button to try again." At this point, i get presented with the same choice as before. From this point on, two things can happen. Either the program freezed tryingg to load, or it crashes. crashing seems more frequent on recovery then on ignoring crash data. | ||||
| Additional Information | I guesstimate a 1/4 ratio on crash versus freeze on using recovery and 1/10 on not using recovery, though these numbers are not scientific. svn r13195 seems to crash on this project for a completely different reason. A file is attached with ardour running with '-D all'. This is running on a dual core athlon x2 system with 4gb of ram on a centos 6 kernel, and the project is expendable, but i saved a copy if you require further analysis. I'll try attaching the .ardour file afterwards. If you anything else please let me know. | ||||
| Tags | No tags attached. | ||||
|
2012-09-30 18:29
|
|
|
2012-09-30 18:31
|
|
|
2012-09-30 18:31
|
|
|
2012-09-30 18:31
|
|
|
|
21:12 < edogawa> nido: anyway i just was able to load your session file with r13200 (of course with empty regions) 21:43 < edogawa> nido: the crash and freeze logs are almost identical, just that crash has one more line in the end with a Glib related error (i mean the IDs are different but the rest of the text is the same) 21:48 < edogawa> nido: just put that .ardour file to somwhere outside the session folder and try to load it from there |
|
|
I tried to load the project with empty regions unsuccesfully first. I restarted jackd with increased buffer size and tried again. beta5 worked without problems. Opening the original project with beta5 worked as well. In the end this was a jack buffer size problem. I changed the status of this bug as resolved |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-09-30 18:29 | nido | New Issue | |
| 2012-09-30 18:29 | nido | File Added: bartekko.ardour | |
| 2012-09-30 18:31 | nido | File Added: ardour-open-svn-r13195.gz | |
| 2012-09-30 18:31 | nido | File Added: ardour-open-crash.gz | |
| 2012-09-30 18:31 | nido | File Added: ardour-open-freeze.gz | |
| 2012-09-30 20:00 | nido | Note Added: 0014032 | |
| 2012-09-30 20:04 | nido | Note Added: 0014033 | |
| 2012-09-30 20:05 | nido | Status | new => resolved |
| 2012-09-30 20:05 | nido | Resolution | open => fixed |
| 2012-09-30 20:05 | nido | Assigned To | => nido |
| 2012-09-30 20:05 | nido | Status | resolved => closed |
