[edgy] firefox crashed [@DocumentViewerImpl::Destroy] [@nsPluginInstanceOwner::Init]

Bug #77222 reported by dimaL
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
High
Mozilla Bugs

Bug Description

Binary package hint: firefox

Running Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy) and after installing sun-java5-jre and plug-in through update manager,
we wanted to check that java works.

The browser crashed.

Revision history for this message
dimaL (lukhtai) wrote :
Revision history for this message
dimaL (lukhtai) wrote :

I was able to load the page correctly. What was different this
time was that I did not resize the browser window while opening.

Thus, it is likely the the resizing caused the crash...

Revision history for this message
elpitagorico (elpitagorico) wrote :
Revision history for this message
elpitagorico (elpitagorico) wrote : Re: [Bug 77222] Re: crash from viewing java-applet containign page runescape.com on a low memory machine

Thank you very much. I solve the problem with your indications.

Bye,

El mié, 27-12-2006 a las 01:47 +0000, dimaL escribió:

> I was able to load the page correctly. What was different this
> time was that I did not resize the browser window while opening.
>
> Thus, it is likely the the resizing caused the crash...
>

David Farning (dfarning)
Changed in firefox:
assignee: nobody → mozillateam
importance: Undecided → Medium
Revision history for this message
Freddy Martinez (freddymartinez9) wrote : Re: crash from viewing java-applet containign page runescape.com on a low memory machine

Can you reproduce this bug?

Changed in firefox:
assignee: mozillateam → freddymartinez9
status: Unconfirmed → Needs Info
Revision history for this message
elpitagorico (elpitagorico) wrote :

I've been trying to repeat this bug, but I didn't get it. This possible
bug happened when I visited
https://www.rafaelhoteles.com/ReservasWEB/reservas_rafael.php . I hope
to help you

Revision history for this message
Alexander Sack (asac) wrote :

crash bugs get at least high importance

Changed in firefox:
importance: Medium → High
Revision history for this message
John Vivirito (gnomefreak) wrote :

elpitagorico Can you please upload the full crash report. I will attempt a retrace on it but without the full report i wont know what version of firefox it crashed with and Retrace may turn up will less symbols.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Taking for retrace.

Changed in firefox:
assignee: freddymartinez9 → gnomefreak
Revision history for this message
John Vivirito (gnomefreak) wrote :

Dimal's Stacktrace

Revision history for this message
John Vivirito (gnomefreak) wrote :
Revision history for this message
John Vivirito (gnomefreak) wrote :
Revision history for this message
John Vivirito (gnomefreak) wrote :

Finished retrace.
elpitagorico The retrace we got looks pretty good you shouldnt need to upload it but if you do i can rerun trace on it.

Changed in firefox:
assignee: gnomefreak → mozillateam
Revision history for this message
elpitagorico (elpitagorico) wrote :

I think the report upload is the full crash report. I can't upload again because report isn't on my computer

Revision history for this message
John Vivirito (gnomefreak) wrote :

the stacktrace looks fine. your report was missing uname section and a few others but the coredump had enough info for me. Thank You for answering

David Farning (dfarning)
Changed in firefox:
assignee: mozillateam → mozilla-bugs
Revision history for this message
John Vivirito (gnomefreak) wrote : Re: MASTER [@DocumentViewerImpl::Destroy] [@nsPluginInstanceOwner::Init]

Dimal your crash is a duplicate of bug #76608. We are gonna use this bug report for elpitagorico as a master bug.

Changed in firefox:
status: Needs Info → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

this bug doesn't qualify as a master. waiting for dupe or testcase.

Changed in firefox:
status: Confirmed → Incomplete
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

We have not received any duplicates for some time. Thus, this crash was likely due to some unique plugin extension combination or has been fixed in the meantime. Please, reopen it at any time if you have more related info.

Thanks for your contribution. Don't hesitate to submit new crashes,

H. Montoliu

Changed in firefox:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.