View Issue Details

IDProjectCategoryView StatusLast Update
0005568ardourbugspublic2013-07-14 15:12
Reporterjacksinthegreen Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
Product Version3.0 
Summary0005568: HD 100%, paging, very slow , then crash
DescriptionUbuntu Studio 12.04 64 bit, Kernel Linux 3.2.0-49-lowlatency, GNOME 3.4.2
ASUS Core i7, 6 GB RAM
Ardour 3.2

I was working on a multitrack for a lot of hours.
Copy & paste of a very small region (3-4 seconds)
The system becomes very slow, almost unresponsive, cpu low (6-7%), but HD spinning 100%. After several minutes Ardour crashes.
Reopening the same session gives the same results.
Checking memory, I see a progressive memory eat, until all memory gets used, the system starts paging up to 3 GB (plus 6 GM RAM) then crashes.

I don't know how to recover the session.

TagsNo tags attached.

  Users sponsoring this issue (Total Sponsorship = US$ 10)

Activities

jacksinthegreen

2013-07-08 03:48

reporter   ~0015076

Last edited: 2013-07-08 04:00

RAM is eaten in about 5-6 seconds, then Linux starts paging and Ardour shows the loading window "Setup Editor" for several minutes, then it crashes.
The same occurs not using Jack.

The .bak session is identical to the main session: thinking of a possible Linux crash, I did a few ctrl-S that overwritten the .bak (and once healthy) copy.

The issue started just after the "copy and paste" of the small region (it was the recording of a single chimes "ping").

p.s.: opening the .ardour file with a text editor gives a perfectly readable file. Knowing the structure of the file, it should be possible to find the bad instruction and remove it. Anybody can help ?

paul

2013-07-08 15:24

administrator   ~0015077

(1) Ardour always uses JACK
(2) You could start by attaching the session file to the bug report
(3) http://ardour.org/debugging_ardour <= we really need a backtrace (or 2) from you to be able to debug this.

2013-07-09 03:25

 

2013-07-09 03:25

 

2013-07-09 04:05

 

ardour.dbg (49,956 bytes)

jacksinthegreen

2013-07-09 04:07

reporter   ~0015082

Last edited: 2013-07-09 05:06

Paul, thank you for your kind reply

1) ok, I didn't know, let's say I run jack from inside Ardour, instead of through qjackctl
2) I uploaded both session and history files
3) I uploaded ardour.dbg file

Best regards

Alessandro

p.s.: the backtrace has been taken from a "fresh" system, just rebooted

2013-07-09 20:03

 

BacktraceNoRealtime (47,929 bytes)   

jacksinthegreen

2013-07-09 20:04

reporter   ~0015084

mmhhh... I left the realtime option on...
Backtrace re-created with realtime off & client timeout 5000

Issue History

Date Modified Username Field Change
2013-07-07 20:36 jacksinthegreen New Issue
2013-07-08 03:48 jacksinthegreen Note Added: 0015076
2013-07-08 04:00 jacksinthegreen Note Edited: 0015076
2013-07-08 04:00 jacksinthegreen Note Edited: 0015076
2013-07-08 15:24 paul Note Added: 0015077
2013-07-09 03:25 jacksinthegreen File Added: Black Bird 3.0beta5.ardour
2013-07-09 03:25 jacksinthegreen File Added: Black Bird 3.0beta5.history
2013-07-09 04:05 jacksinthegreen File Added: ardour.dbg
2013-07-09 04:07 jacksinthegreen Note Added: 0015082
2013-07-09 04:09 jacksinthegreen Note Edited: 0015082
2013-07-09 04:11 jacksinthegreen Sponsorship Added jacksinthegreen: US$ 10
2013-07-09 04:11 jacksinthegreen Sponsorship Total 0 => 10
2013-07-09 04:14 jacksinthegreen Note Edited: 0015082
2013-07-09 05:06 jacksinthegreen Note Edited: 0015082
2013-07-09 05:06 jacksinthegreen Note Edited: 0015082
2013-07-09 20:03 jacksinthegreen File Added: BacktraceNoRealtime
2013-07-09 20:04 jacksinthegreen Note Added: 0015084