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 434050 - totem crashes on videos that are higher resolution than my monitor from stage6.divx.com
totem crashes on videos that are higher resolution than my monitor from stage...
Status: RESOLVED DUPLICATE of bug 351784
Product: totem
Classification: Core
Component: Browser plugin (obsolete)
2.18.x
Other All
: High critical
: ---
Assigned To: totem-browser-maint
totem-browser-maint
Depends on:
Blocks:
 
 
Reported: 2007-04-28 07:23 UTC by gregh
Modified: 2007-05-10 14:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gregh 2007-04-28 07:23:40 UTC
Steps to reproduce:
1. download or get a video from stage6.divx.com that is higher resolution than your monitor
2. play video through totem or totem web browser (streamed or downloaded doesn't make difference)
3. totem will crash immediately after

Stack trace:


Other information:
Comment 1 Philip Withnall 2007-04-28 13:56:01 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://www.gnome.org/projects/totem/#bugs for more information on how to do so. Thanks in advance!
Comment 2 gregh 2007-04-28 16:11:59 UTC
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 48 error_code 11 request_code 141 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.)
Comment 3 palfrey 2007-04-28 18:26:02 UTC
(In reply to comment #2)
> The program 'totem' received an X Window System error.
> This probably reflects a bug in the program.

This is unfortunately not a stacktrace. Please see http://live.gnome.org/GettingTraces/Details#learn-about-stacktraces for details about what a stacktrace is and isn't, as well as further down that page for instructions on "Obtaining a stack trace". Without a good stacktrace, we can't fix the problem.
Comment 4 gregh 2007-04-28 19:09:35 UTC
Wasn't able to get stacktrace working. it just ends up giving me the same info I already posted. 

I found something new about the crash though, as long as totem is minimized and I haven't had the video play at all none-minimized it works. Not able to see the video though but sound works perfectly. Even after the video ends, when I unminimized it, it crashes.

I hope that helps until I can get the stacktrace. I'll try some other debugging programs. Any other recommendations other than gdb.

Comment 5 gregh 2007-04-29 01:22:17 UTC
I learned something new, having a second totem open makes the movies not crash.
Comment 6 palfrey 2007-04-29 10:52:32 UTC
(In reply to comment #4)
> Wasn't able to get stacktrace working. it just ends up giving me the same info
> I already posted. 

Can you try following the instructions from the error? Specifically, run gdb as "gdb --args totem --sync filename" where "filename" is the file that crashes totem. Once you're at the gdb prompt, before typing "run", enter in the command "br gdk_x_error". Gdb may respond with the question:

Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) 

Answer 'y' to this if you see it, and then type "run".
Comment 7 Bastien Nocera 2007-05-10 14:57:57 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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