GNOME Bugzilla – Bug 347761
X window error when clicking on stop (about 1 or 2 sec after the "save video" dialog pops up)
Last modified: 2007-02-22 15:04:22 UTC
Steps to reproduce: 1. run istanbul 2. click on record 3. click again to stop 4. wait a couple of seconds for the "save video" dialog to pop up, istanbul will shut itself down entirely Stack trace: remi@atmos ~ $ istanbul && echo ok widget: <gtk.CheckMenuItem object (GtkCheckMenuItem) at 0xb70bd2d4> SaveWindow with file: /tmp/tmpXPFs2b The program 'istanbul' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 43 error_code 11 request_code 142 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Other information: It doesn't seem to be segfaulting. It's just quitting.
My tiny comment to confirm this, I encountered this error too. I had to quit my X session, and restart it, then istanbul worked properly. I hope it helps.
Do you guys get this with latest CVS?
Found it ! I used a one liner to print final_pipeline in istanbul/main/screencast.py and run things manually from the command line. Everything works fine. It's when I try to play the saved video that problems arise. Totem fails with *exactly* the same error as Istanbul. MPlayer too. So I tried switching video output devices, (-vo xv => -vo x11 in MPlayer, autovideosink to ximagesink in gst-preferences) and *behold* the videos plays perfectly. Running Istanbul again with ximagesink instead of autovideosink prevents the crash. Maybe ximagesink should be hard coded in Istanbul until xvimagesink is fixed ? Maybe there's a way to handle this gracefully ?
Forgot to say that this was done using the latest CVS. I'll bet it'll work with 0.0.2 too.
Remi, this is because of a bad X driver that you have maybe. I still think istanbul should respect whatever the selected video output of the user, just like totem does. I wonder if there is a check you can do with Xv to tell if it would fail like this before using it.
I'm using i810 from Xorg 7.1 and gentoo-sources-2.6.17 in Gentoo. If this one is buggy ... I can't imagine how the others compare. :) OTOH, I only have 32megs of system ram set aside for the i855 chipset on my laptop. Xorg already uses a larg chunk of that for its own needs, so maybe there isn't much left for Xv (at least not enough to play a video this size). Is there anyone in Gnome that would know more about this? Should I contact upstream?
I am using the same driver under Xorg 7.1. What size video are you trying to play with Xv? Maybe i should check based on size and Xv availability if the gconf key is set to xvimagesink. Eric Anholt would know about this possibly, he works for intel on the i810 driver in xorg.
I have exactly the similar hardware, software, and the same bug in full screen recording. The X resolution used is 1400x1050.
I have set this to be forced to be ximagesink. So is now fixed in CVS.
*** Bug 399121 has been marked as a duplicate of this bug. ***