firefox crashed

Bug #131793 reported by Ernesto Ruge
4
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Medium
Alexander Sack
firefox-3.0 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

... firefox crashes / makes ghostscript errors when printing spiegel.de in a postscript

if i try to print www.spiegel.de into a postscript firefox makes 100% usage in gutsy alpha4 all updates. in feisty you get an strange ghostscript error (abnormal process termination).

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Report Needed

Thank you Infinity for submitting this report and sorry for this late
response.

Is this still an issue for you?

Could you please try to obtain a backtrace by following the instructions
on [1], or upload the crash report that probably was generated during
the crash and that should be located at /var/crash/ to [2].

Please indicate which extensions/plugins do you have enabled; and if
this crash is reproducible describe the steps that lead to it (it is
very important for us to have a test case for each crash).

This will greatly aid us in tracking down your problem.

Thanks in advance.

H. Montoliu

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs
[2] https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/131793/+addcomment

description: updated
Changed in firefox:
assignee: nobody → mozilla-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Ernesto Ruge (the-infinity) wrote :

It is still an issue. (Works with 7.04 and a fresh installed gutsy alpha5)

It is a crash in the way that it uses 100% CPU and reacts on nothing, an infinite loop. So I can't give a backtrace.

There are no plugins installed, its just a fresh kubuntu 7.10 alpha5 installation with firefox installed afterwards.

Everyone I asked was able to confirm it, so I would say - just try it for yourself. Go to www.spiegel.de, then file -> print, Use Postscript/default as printer - and see how ghostscript crashes. Some time ago I got an ghostscript error message, now I (and some other people) just get the loop ...

But I just got information that Epiphany also loops (100% CPU usage -> no reaction). Konqueror does not.

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

can you identify a regression window? when did it last work for you in gutsy?

Changed in firefox:
assignee: mozilla-bugs → asac
Revision history for this message
Ernesto Ruge (the-infinity) wrote :

It never worked as far I know. I found the bug as I wanted to show my mother how to make postscripts of spiegel online - it is a german on- and offline newsletter. My mother has kubuntu 7.04, I just tested it in kubuntu 7.10 - all the time the same bug. I also asked several persons in IRC with german ubuntu and kubuntu - everyone could confirm it with firefox and epiphany.

And what is a regression window (sorry for my bad english ;) ) ... a status bar or something like that? ... the only thing I get is if I want to close firefox "application does not react - do you want to close it anyway?"

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 131793] Re: firefox crashed

On Sat, Sep 01, 2007 at 12:36:08PM -0000, Infinity wrote:
> It never worked as far I know. I found the bug as I wanted to show my
> mother how to make postscripts of spiegel online - it is a german on-
> and offline newsletter. My mother has kubuntu 7.04, I just tested it in
> kubuntu 7.10 - all the time the same bug. I also asked several persons
> in IRC with german ubuntu and kubuntu - everyone could confirm it with
> firefox and epiphany.
>
> And what is a regression window (sorry for my bad english ;) ) ... a
> status bar or something like that? ... the only thing I get is if I want
> to close firefox "application does not react - do you want to close it
> anyway?"
>

Can you try if you see the same in gnome? There are issues with the
gtk-qt engine (which makes firefox look well under kde). I doubt that
this is the reason, but its worth a look at last.

Forget about the regression window ... it means, do we know when this
bug was introduced. But since you said that it never worked, it
appears to be not a regression at all.

 - Alexander

Revision history for this message
Ernesto Ruge (the-infinity) wrote :

I just asked some people in #ubuntu+1 channel with gnome - and they could also let firefox hang. And I also got following info:

> penguin42: TheInfinity: Seems to be in libgklayout.so

... seems to be a problem with gtk in general ... ?

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

On Sat, Sep 01, 2007 at 09:33:46PM -0000, Infinity wrote:
> I just asked some people in #ubuntu+1 channel with gnome - and they
> could also let firefox hang. And I also got following info:
>
> > penguin42: TheInfinity: Seems to be in libgklayout.so
>
> ... seems to be a problem with gtk in general ... ?
>

Which theme did they use?

 - Alexander

Revision history for this message
Kjell Braden (afflux) wrote :

Can confirm this on current hardy, with firefox 3.0~b4+nobinonly-0ubuntu1. Apport showed up when I killed firefox, I'm uploading the report now.

Changed in firefox:
status: Incomplete → Confirmed
Revision history for this message
Kjell Braden (afflux) wrote :

The report I got was incomplete, so I can't provide a valid backtrace.

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

there is a section about crashes here:

https://wiki.ubuntu.com/MozillaTeam/Bugs

follow that to get a backtrace manually.

Revision history for this message
Stephan Rügamer (sruegamer) wrote :
Download full text (5.3 KiB)

As Discussed on IRC....old way of getting backtraces:)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7d116c0 (LWP 20208)]
0xb72f4e9c in nsGfxScrollFrameInner::AsyncScrollPortEvent::Run (this=0xa00de00)
    at ./../base/nsPresContext.h:182
182 ./../base/nsPresContext.h: No such file or directory.
 in ./../base/nsPresContext.h
Current language: auto; currently c++

#0 0xb72f4e9c in nsGfxScrollFrameInner::AsyncScrollPortEvent::Run (this=0xa00de00)
    at ./../base/nsPresContext.h:182
No locals.
#1 0xb7912e4a in nsThread::ProcessNextEvent (this=0x809e450, mayWait=1, result=0xbffaf090)
    at nsThread.cpp:510
 notifyGlobalObserver = 1
 obs = {<nsCOMPtr_base> = {mRawPtr = 0x8132bb4}, <No data fields>}
 event = {<nsCOMPtr_base> = {mRawPtr = 0xa00de00}, <No data fields>}
 rv = 0
#2 0xb78e242b in NS_ProcessNextEvent_P (thread=0x3, mayWait=1) at nsThreadUtils.cpp:227
 val = <value optimized out>
#3 0xb7864826 in nsBaseAppShell::Run (this=0x8132bb0) at nsBaseAppShell.cpp:170
 thread = (class nsIThread *) 0x809e450
#4 0xb76f9826 in nsAppStartup::Run (this=0x8190610) at nsAppStartup.cpp:181
 rv = <value optimized out>
#5 0xb7154722 in XRE_main (argc=1, argv=0xbffb03f4, aAppData=0x805e038) at nsAppRunner.cpp:3154
 obsService = {<nsCOMPtr_base> = {mRawPtr = 0x81170c8}, <No data fields>}
 remoteService = {<nsCOMPtr_base> = {mRawPtr = 0x8871e28}, <No data fields>}
 appStartup = {<nsCOMPtr_base> = {mRawPtr = 0x8190610}, <No data fields>}
 workingDir = {<nsCOMPtr_base> = {mRawPtr = 0x831e110}, <No data fields>}
 chromeObserver = {<nsCOMPtr_base> = {mRawPtr = 0x80bf870}, <No data fields>}
 cmdLine = {<nsCOMPtr_base> = {mRawPtr = 0x82a27a0}, <No data fields>}
 noEMRestart = <value optimized out>
 xpcom = {mServiceManager = 0x80a088c}
 desktopStartupIDEnv = <value optimized out>
 desktopStartupID = {<nsFixedCString> = {<nsCString> = {<nsACString_internal> = {<nsCSubstring_base> = {<No data fields>}, mData = 0xbffaf508 "", mLength = 0,
        mFlags = 65553}, <No data fields>}, mFixedCapacity = 63, mFixedBuf = 0xbffaf508 ""},
  mStorage = "\000���?�\222�`�\005\b��\004\b8���\200�\222�D���\001\000\000\000�x\220���\004\b(���\\�\005\bX���H�\004\b(���\000\000\000"}
 xremotearg = <value optimized out>
 upgraded = 0
 appInitiatedRestart = <value optimized out>
 dirProvider = {<nsIDirectoryServiceProvider2> = {<nsIDirectoryServiceProvider> = {<nsISupports> = {
        _vptr.nsISupports = 0xb7aec268}, <No data fields>}, <No data fields>}, <nsIProfileStartup> = {<nsISupports> = {_vptr.nsISupports = 0xb7aec28c}, <No data fields>},
  mAppProvider = {<nsCOMPtr_base> = {mRawPtr = 0x0}, <No data fields>},
---Type <return> to continue, or q <return> to quit---
  mGREDir = {<nsCOMPtr_base> = {mRawPtr = 0x805e260}, <No data fields>},
  mXULAppDir = {<nsCOMPtr_base> = {mRawPtr = 0x805e1b8}, <No data fields>},
  mProfileDir = {<nsCOMPtr_base> = {mRawPtr = 0x80a52e8}, <No data fields>},
  mProfileLocalDir = {<nsCOMPtr_base> = {mRawPtr = 0x80a5368}, <No data fields>},
  mProfileNotified = 1 '\001', mExtensionsLoaded = 1 '\001',
  mAppBundleDirectories = {<nsCOMArray_base> = {mArray = {mI...

Read more...

Changed in firefox:
status: Invalid → Confirmed
Revision history for this message
Stephan Rügamer (sruegamer) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

crash appears to be gone in 3.0 RC1 currently in proposed.

Changed in firefox:
status: Confirmed → Fix Committed
Changed in firefox-3.0:
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
Alexander Sack (asac) wrote :

fixing status. its firefox 3 that is fix committed

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

could anyone please test latest ffox 2 available in gutsy?

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

On Wed, Jun 04, 2008 at 02:42:09PM -0000, Stephan Hermann wrote:
> As Discussed on IRC....old way of getting backtraces:)
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb7d116c0 (LWP 20208)]
> 0xb72f4e9c in nsGfxScrollFrameInner::AsyncScrollPortEvent::Run (this=0xa00de00)
> at ./../base/nsPresContext.h:182
> 182 ./../base/nsPresContext.h: No such file or directory.
> in ./../base/nsPresContext.h
> Current language: auto; currently c++
>
>
> #0 0xb72f4e9c in nsGfxScrollFrameInner::AsyncScrollPortEvent::Run (this=0xa00de00)
> at ./../base/nsPresContext.h:182

should be here
http://lxr.mozilla.org/seamonkey/source/layout/generic/nsGfxScrollFrame.cpp#1929

Can you see if and what is null or bogus mem for
mInner->mOuter->PresContext()->GetPresShell() ?

 - Alexander

Detriot83 (ladykelly71)
Changed in firefox:
assignee: asac → ladykelly71
Revision history for this message
Kjell Braden (afflux) wrote :

Detriot83, please only assign bugs to yourself when you're really working on them (they should be inprogress then).

Changed in firefox:
assignee: ladykelly71 → asac
Revision history for this message
Kjell Braden (afflux) wrote :

Closing as no further information was provided.

Changed in firefox:
status: Incomplete → Invalid
Przemek K. (azrael)
Changed in firefox-3.0 (Ubuntu):
status: Fix Committed → Fix Released
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.