Pitivi crashes when adding a mov file to the timeline

[Alan Pope 🍺🐧🐱 🦄]

Binary package hint: pitivi

I seem to be able to reliably crash pitivi by dragging mov files from my iphone into the timeline. I captured a debug log as per http://www.pitivi.org/?go=bugs and have attached it.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: pitivi 0.13.5-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Jan 26 23:23:34 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LC_MESSAGES=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: pitivi

[Jeff Fortin Tam (kiddo)]

Could you attach a sample file?
However I suspect the file isn't the problem, because I saw this in the debug log:

Gdk-ERROR **: 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 61 error_code 11 request_code 132 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.)
aborting...

Which sounds like a video driver problem or an out of memory error? Not sure...

[Alan Pope 🍺🐧🐱 🦄 (popey)]

Sample video attached.

[Jeff Fortin Tam (kiddo)]

Tested with your sample file, and had no problem importing it, inserting
in the timeline and seeking/playing it (both on pitivi 0.13.5 and pitivi
git)... Have you been able to reproduce this on machines with different
hardware configurations?

[Brian Murray (brian-murray)]

I was unable to recreate this crash however I am not running unity on the system I was testing with. Alan I'd be interested to know what happens if you try to recreate the bug with a non unity session.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

After todays update I can't reproduce it either in unity or classic GNOME. I'll mark invalid for now and reopen if it happens again. Thanks!