View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000875 | ardour | bugs | public | 2005-02-02 18:01 | 2008-11-20 23:43 |
| Reporter | litlnemo | Assigned To | paul | ||
| Priority | normal | Severity | crash | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Summary | 0000875: Ardour/GTK 0.565.2 running with libardour 0.861.3 (hey my version of ardour: beta24 is not on the list!!) | ||||
| Description | Gtk-CRITICAL **: file gtkcontainer.c: line 730 (gtk_container_remove): assertion `widget->parent == GTK_WIDGET (container)' failed. I was editing graphically ardour, moving the scrollbars and more things. But I cannot remmeber the moment it happened. Ardour crashes a lot in my computer. I cannot edit any song, even at high latency. At low latencies is even worst (one crash per minute)... I think you should do as firefox and the kde crew do: when ardour crashes, package the trace and display a window asking to send it to the developpers. Now it's very difficult to report this kind of bugs and ardour is so unstable that it's impossible to use it seriously (IMHO)... ;) Another thing is that I think that GTK is becoming a nightmare to ardour developpers. Please switch to GTK2 before releasing a stable version or you will never reach it... | ||||
| Additional Information | upgraded to debian testing in a 686-smp computer, 512Mb RAM, an audigy. | ||||
| Tags | No tags attached. | ||||
|
|
well now I realise that I have been a little bit aggressive... I'm sorry. I also have to say that you've done a great great work. It's just that I'm dying to record in linux better and throw away my windows box... that's why I become exhasperated you know? you all know better than me why do you continue with GTK to do the stable realease... my words are only about what a person "in the street" says about it. the real issue that I wanted to report is the crash. |
|
|
well, lets see. you can start by sending us the your own trace. don't have one? thats because ardour builds without debugging enabled by default - there is a 30-50% performance difference, and unlike mozilla, that kind of thing has huge implications for the program and its users. you can compile ardour with debugging enabled if you build it from source using ./configure --disable-optimize; a few packagers are making debug versions available. however, there is no trace without gdb either; the kind of trace ardour itself could write is essentially useless to us. so you also have to use gdb to get a useful trace for us to analyse. finally, most of the time gdb backtraces simply tell me that there is memory corruption, and provides no clue as to where it happened. i have to run valgrind to get further on that front. all of this is an attempt to explain why we do not offer the kind of facilities that mozilla does. second, although its not certain, your problems with ardour are not typical of most people's experience with the program right now. there are a number of people who have unusual problems that we cannot track down, and this could indicate a problem in the program, in the build process or on their systems. it is very hard to explain the kind of problem you are reporting when there are people recording 17 song, 11-track sessions of a 5 piece rock group in a couple of days with *zero* issues. does it mean ardour is not to blame? no. does it mean that it will take a lot of work to track down the problem? yes. does it mean that it might be your system? yes. finally, about GTK. porting to GTK2 will be a significant effort on our part. We want to remain focused on fixing bugs that interfere with first time usage and ensuring that ardour is usable for end-to-end production of music with few significant issues for typical cases. when that is done (and it almost is), we will release 1.0 and then *immediately* fork the gtk_ardour directory and port to GTK2. we want to a GTK2 version at least as much any users want us to, but it would be a mistake right now when there are significant basic things we have to get right. i would appreciate it if it was possible for you to build a debug version of ardour and get some gdb backtraces (how to do so is described in the FAQ). you can attach them to this report later. i understand that compiling ardour from source is hard to do, so if its not what you are doing already, it may not be an option for you. |
|
|
Thank you for being so comprenhensive. Yesterday, with the second post, I already started to think that there should be some things that I couldn't understand... I was also in a bad mood... So I'll try to be more constructive and try to help fixing crashes. That's the better way to get faster to the GTK2 :) Now I run in a debian testing, using the binaries. I'll download the ardour sources and install them in a directory apart. This will cause me conflict with the existing ardour from binaries if I run it as ./ardour at this directory? (I mean loading external libraries or something similar). But this will take me some time. By now, I can send you the concrete project that crashes with ardour. It was done with previous versions of ardour and maybe this is the reason for these inusual crashes (I didn't know that other users were running ardour without problems). I start jack with: /usr/bin/jackd -p60 -t10000 -dalsa -dhw:0 -r44100 -p2048 -n2 -S -i1 -o2 I start ardour. I open session "newlife" (this is the stupid name of the song, which I don't change because I never haven't found a way in ardour to do it). I play it. And it crashes *always* at 1min:29s or 45|01|etc. Jack displays: "**** alsa_pcm: xrun of at least 9998.412 msecs" But the most surprising thing is that only dragging the cursor to that position makes ardour crash! I drag it and after leaving it after the mark of 1min:29s, ardour immediately crashes. I attach you the session file. Tell me what kind of information do you want me to send you about my system. (for example you can send me a script which outputs it into a text file) You may need to know also that I have also "downdated" my kernel from 2.6.10 to 2.6.9 to avoid issues from this kernel which is yet unstable and I run jack without realtime priority (when I edit the tracks, not for recording, where I use kernel-multimedia). |
|
2005-02-03 19:11
|
|
|
|
I have not uploaded the wav files for obvious reasons. If you want some of them just ask me... I can upload them in my web page if it's necessary. |
|
|
FIXED with ardour-beta26. No more bug. You can close it. |
|
|
see bugnotes for history. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-02 18:01 | litlnemo | New Issue | |
| 2005-02-02 18:01 | litlnemo | => marc_contrib@ramonvinyes.es | |
| 2005-02-02 18:01 | litlnemo | Name | => MarC |
| 2005-02-02 21:53 | litlnemo | Note Added: 0001955 | |
| 2005-02-03 12:22 | paul | Note Added: 0001957 | |
| 2005-02-03 19:09 | litlnemo | Note Added: 0001961 | |
| 2005-02-03 19:11 | litlnemo | File Added: newlife.zip | |
| 2005-02-03 19:28 | litlnemo | Note Added: 0001962 | |
| 2005-02-12 16:35 | litlnemo | Note Added: 0001990 | |
| 2005-02-12 16:44 | paul | Status | new => resolved |
| 2005-02-12 16:44 | paul | Resolution | open => fixed |
| 2005-02-12 16:44 | paul | Assigned To | => paul |
| 2005-02-12 16:44 | paul | Note Added: 0001991 | |
| 2008-11-20 23:43 | seablade | Status | resolved => closed |
