268611 - Crash every time on digicrime.com [@ libgobject-2.0.so.0 - mplayerplug-in.so]

Status: RESOLVED EXPIRED

(Plugins Graveyard :: Mplayer, defect)

Description

[Leo H]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041030 Firefox/1.0RC2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041030 Firefox/1.0RC2

Going to digicrime.com crashes Firefox every single time.

Reproducible: Always
Steps to Reproduce:
1. Go to digicrime.com
2. Java applet pops up that takes up the whole screen
3. Browser crashes

Actual Results:  
Browser crashes

Expected Results:  
Browser does not crash

Talkback reports are shown as "Queued" - I don't know how to attach them to this
bug.

Comment 1

[Bernard Alleysson]

right click on the incident, then "Copy" and paste the talkback ID into this bug

Comment 2

[Patrick]

what java vm do you have installed?

in firefox, go to "about:plugins" and look for Java.

Methinks it's Java related. Under tools - options - web features - uncheck the
ENABLE JAVA and try the site again please?

Comment 3

[Alessio]

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041030 Firefox/1.0RC2
> Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041030 Firefox/1.0RC2
> 
> Going to digicrime.com crashes Firefox every single time.

Hmmm, interesting... When i open that site, my antivirus guard (AntiVir 6) warns
me with this message:
"Contains signature of the joke program Joke/BlueScreen.Jav"
and asks if i want to execute the applet or not...

Anyway either answering no or yes, my Mozilla 1.7.3 on Win XP Pro doesn't crash.

Comment 4

[Patrick]

fwiw: i don't have a java vm installed for Firefox.

Comment 5

[Hermann Schwab]

(In reply to comment #0)

> Talkback reports are shown as "Queued" - I don't know how to attach them to this
> bug.

Queued means, they couldn´t be sent to the talkback server, Mozilla or Firefox
will try next time at start.
Possible reasons:
- server down
- server busy
- firewall blocks talkback
- proxy blocks talkback

open talkback, click on Incident, and then  'Send queued incidents        Ctrl+S'
after message has been delivered, the server sends back a Talkback ID.
If you don´t succeed, and use a proxy, see the link below how to configure
Talkback to use the proxy, and some more info about talkback.
http://www.mozilla.org/quality/qfa.html


You can then use the comment below, or Edit/SelectAll/Copy currently selected
Incident IDs ... to copy & paste the IDs to this bug.

There is also a slight chance your reports got transmitted, but you didn´t
receive the TalkbackIds. ( happened to me once )
Seems that in this case the server doesn´t accept your retries to send these
reports. If you did comment the reports, put a URL into the URL field, or
comment field, and/or wrote a short comment, you can search for the reports at
http://talkback-public.mozilla.org/talkback/fastfind.jsp

Use the 'Search By:' function, check '[x] Comments' or check '[x] URL'


before you start your search, look if there is a Talkback Server Update at the
footer of the page. Currently there is:
>There are currently 444 incidents waiting to be processed by the Talkback server.
> The next incident id in the queue is 1860997 and was submitted on 2004-11-10
12:52:33.0.

This means if you report was sent after this date and time, it isn´t yet
processed and ready to be found or seen.


(In reply to comment #1)
> right click on the incident, then "Copy" and paste the talkback ID into this bug

works only, if the reports have been sent. Queued reports are waiting to be sent.

Comment 6

[Leo H]

I am using Java(TM) Plug-in 1.4.2_03-b02
I think I have the Talkback IDs:
TB1832015E
TB1832013Q
TB1754675Q

Comment 7

[timeless]

reporter: spiffy, you crashed two different plugins

mplayerplug-in and realplayer10 (or helix player community, whatever).

i'm going to focus this on the mplayer plugin since you crashed it twice.

libgobject-2.0.so.0 + 0x23252 (0x00abb252)
mplayerplug-in.so + 0x104ed (0x02d894ed)
mplayerplug-in.so + 0x18c04 (0x02d91c04)
libglib-2.0.so.0 + 0x24b33 (0x0536fb33)
libglib-2.0.so.0 + 0x21fdd (0x0536cfdd)
libglib-2.0.so.0 + 0x22fd8 (0x0536dfd8)
libglib-2.0.so.0 + 0x232ef (0x0536e2ef)
libglib-2.0.so.0 + 0x239cf (0x0536e9cf)
libgtk-x11-2.0.so.0 + 0xd144f (0x002cc44f)
nsAppShell::Run() 
[/builds/tinderbox/firefox-1.0/Linux_2.4.20-28.8_Clobber/mozilla/widget/src/gtk2/nsAppShell.cpp,
line 144]
nsAppShellService::Run() 
[/builds/tinderbox/firefox-1.0/Linux_2.4.20-28.8_Clobber/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 495]
xre_main() 
[/builds/tinderbox/firefox-1.0/Linux_2.4.20-28.8_Clobber/mozilla/toolkit/xre/nsAppRunner.cpp,
line 692]
main() 
[/builds/tinderbox/firefox-1.0/Linux_2.4.20-28.8_Clobber/mozilla/browser/app/nsBrowserApp.cpp,
line 59]
libc.so.6 + 0x15770 (0x005c8770)

if at all possible, please find contact info for your plugins and report the
problems to them. also if you could reduce the problem to a small set of files
(preferably a tiny html file and a single external resource), that'd help
everyone. when you manage to do that, attach the external resource(s) first, and
then modify the html file to reference the attachments at this bugzilla and
attach it.

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.