After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 424983 - insufficient ressources crash on switch to advanced timeline
insufficient ressources crash on switch to advanced timeline
Status: RESOLVED DUPLICATE of bug 339895
Product: pitivi
Classification: Other
Component: General
Git
Other Linux
: Normal critical
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-31 20:58 UTC by Jean-François Fortin Tam
Modified: 2007-04-17 08:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2007-03-31 20:58:29 UTC 
I have a centrino laptop with an i915 (128mb) video card on it. I also tried on my desktop that has 1gb of RAM and a geforce FX5200 (128mb). The computers are not running a composited desktop.

This happens when I import a clip into the timeline and click to switch to advanced view. It is a regression.

The program 'pitivi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 74979 error_code 11 request_code 53 minor_code 0)
  (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.)
Comment 1 Edward Hervey 2007-04-01 10:07:59 UTC 
Does that happen with all kind of videos ? Or just with very big ones ?
Comment 2 Jean-François Fortin Tam 2007-04-01 13:39:19 UTC 
just with very big ones actually, a 1 hour recording weighting 700mb
Comment 3 Edward Hervey 2007-04-13 17:59:59 UTC 
yeah, this is a painful bug. It's because we allocate huge gtk widgets.

We could solve this by using a proper canvasing system. I didn't use the existing gnomecanvas since it's not cairo-based. The most promising one seems to be goocanvas, on which Johan was looking at recently.
Comment 4 Edward Hervey 2007-04-17 08:47:20 UTC 

*** This bug has been marked as a duplicate of 339895 ***