totem-mozilla-flash crash Yahoo! Music Video Player BETA

I've already reported this to the Yahoo! director of the project so they'd be looking as well.

Attaching Firefox core-dump.

Thank you for the bug. From the backtrace that looks like a GTK crasher

Debug backtrace from the crash file retraced:

Core was generated by `/usr/lib/totem/totem-mozilla-viewer --xid 46403853 --width 400 --height 300 --u'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7abcaaf in IA__gtk_icon_set_render_icon (icon_set=0x82c1e90, style=0x80f6700, direction=GTK_TEXT_DIR_LTR,
    state=GTK_STATE_PRELIGHT, size=GTK_ICON_SIZE_BUTTON, widget=0x80f8d70, detail=0x0) at gtkiconfactory.c:1470

warning: Source file is more recent than executable.
1470 g_warning ("Error loading theme icon for stock: %s", error->message);
(gdb) bt
#0 0xb7abcaaf in IA__gtk_icon_set_render_icon (icon_set=0x82c1e90, style=0x80f6700, direction=GTK_TEXT_DIR_LTR,
    state=GTK_STATE_PRELIGHT, size=GTK_ICON_SIZE_BUTTON, widget=0x80f8d70, detail=0x0) at gtkiconfactory.c:1470
#1 0xb7c0f8d3 in IA__gtk_widget_render_icon (widget=0x80f8d70, stock_id=0x82e01f0 "gtk-ok", size=GTK_ICON_SIZE_BUTTON,
    detail=0x0) at gtkwidget.c:5572
#2 0xb7ad16fe in gtk_image_expose (widget=0x80f8d70, event=0x80d4298) at gtkimage.c:1638
#3 0xb7af5b00 in _gtk_marshal_BOOLEAN__BOXED (closure=0x80dd540, return_value=0xbf9ac650, n_param_values=2,
    param_values=0xbf9ac72c, invocation_hint=0xbf9ac63c, marshal_data=0xb7ad1160) at gtkmarshalers.c:84
#4 0xb72d3fb9 in g_type_class_meta_marshal (closure=0x80dd540, return_value=0xbf9ac650, n_param_values=2,
    param_values=0xbf9ac72c, invocation_hint=0xbf9ac63c, marshal_data=0xc8) at gclosure.c:567
#5 0xb72d587d in IA__g_closure_invoke (closure=0x80dd540, return_value=0xbf9ac650, n_param_values=2,
    param_values=0xbf9ac72c, invocation_hint=0xbf9ac63c) at gclosure.c:490
#6 0xb72e61e3 in signal_emit_unlocked_R (node=0x80df600, detail=0, instance=0x80f8d70, emission_return=0xbf9ac8ec,
    instance_and_params=0xbf9ac72c) at gsignal.c:2478
#7 0xb72e6e7f in IA__g_signal_emit_valist (instance=0x80f8d70, signal_id=52, detail=0, var_args=<value optimized out>)
    at gsignal.c:2209
...

Does it happen every time? Does it happen without the adobe flash player?

It has happened to me every time on that site. I've been using the Flash player for about 12 hours now. And is the only real blocker to fix Bug #1 on my desktop. To hear Yahoo! Music is the only blocker for me to kiss the closed source OS goodbye.
I cannot test the Yahoo! Video player without Flash on Ubuntu and I usually have the page running all the time on the background and it has crashed on me pretty badly two times in a couple of hours.

Sebastien,

This is related to Bug #80410

I left the crash attachment on that one uploading overnight (it's pretty big at around 26 MB) but I encountered a 500 error on Malone this morning before coming to the office.

Do you know how can I involve Mozilla team on this one?

Thanks in advance,
Alex

Sebastien,

I keep getting a 500 server error when trying to upload the .crash here.

Please let me know where/how to upload it.

Thanks in advance,
Alex

Looks I clicked a button I shouldn't and reopened this to totem. Sorry about that.

Alex

How do I upload the 26 Mb .crash?

Thanks in advance

you use the "include attachment" from the bug page

you can also install the debug packages locally, use apport-retrace and attach the light version of the crash

Crashed again.

This time the .crash is smaller.

Trying to re-attach.

And the latest core dump.

Sebastien,

Can you merge this one with Bug #80410 ?
It's actually the same thing I guess. Also can you elaborate on the debug packages or point me to a general Ubuntu debugging guide so I can get into it myself.

Thanks in advance,
Alex

I've marked the other bug duplicate. For debugging informations you can read https://wiki.ubuntu.com/DebuggingProgramCrash, apport-retrace can be used on a crash file once the debug packages installed to get a debug backtrace

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.