Closed Bug 273716 Opened 20 years ago Closed 20 years ago

segfault trying to print http://www.auto-amd.com/find.asp

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: phil, Assigned: bugzilla)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041207 Firefox/1.0 (Debian package 1.0-5)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041207 Firefox/1.0 (Debian package 1.0-5)

Go to http://www.auto-amd.com/find.asp

Trying to print to a printer causes the browser to crash with a segfault.

Reproducible: Always
Steps to Reproduce:
Backtrace from coredump follows:

(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x4117dd17 in raise () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x08055f5a in nsProfileLock::FatalSignalHandler ()
#3  <signal handler called>
#4  0xb6f30d56 in nsViewManager::RenderViews ()
   from /usr/lib/mozilla-firefox/components/libgklayout.so
#5  0xb6f3531b in nsViewManager::AddRectToDirtyRegion ()
   from /usr/lib/mozilla-firefox/components/libgklayout.so
#6  0xb6c5fdb2 in nsSimplePageSequenceFrame::SetPageNumberFormat ()
   from /usr/lib/mozilla-firefox/components/libgklayout.so
#7  0xb6d593c1 in nsPrintEngine::PrintPage ()
   from /usr/lib/mozilla-firefox/components/libgklayout.so
#8  0xb6d5cea0 in nsPagePrintTimer::StartTimer ()
   from /usr/lib/mozilla-firefox/components/libgklayout.so
#9  0xb7f458de in nsTimerImpl::Fire ()
   from /usr/lib/mozilla-firefox/libxpcom.so
#10 0xb7f45984 in handleTimerEvent () from /usr/lib/mozilla-firefox/libxpcom.so
#11 0xb7f412c7 in PL_HandleEvent () from /usr/lib/mozilla-firefox/libxpcom.so
#12 0xb7f411f4 in PL_ProcessPendingEvents ()
   from /usr/lib/mozilla-firefox/libxpcom.so
#13 0xb7f42e59 in nsEventQueueImpl::NotifyObservers ()
   from /usr/lib/mozilla-firefox/libxpcom.so
#14 0xb7ba0b65 in nsBaseWidget::FreeNativeData ()
   from /usr/lib/mozilla-firefox/components/libwidget_gtk2.so
#15 0xb7e002bf in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#16 0xb7ddac02 in g_main_depth () from /usr/lib/libglib-2.0.so.0
#17 0xb7ddbcf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0xb7ddc030 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb7ddc673 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#20 0x4b4cc4e3 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#21 0xb7ba0f96 in nsAppShell::ReleaseGlobals ()
   from /usr/lib/mozilla-firefox/components/libwidget_gtk2.so
#22 0xb7bf4da4 in ?? ()
   from /usr/lib/mozilla-firefox/components/libnsappshell.so
#23 0x080c8140 in ?? ()
#24 0x0805942c in data_start ()
#25 0xbffffab8 in ?? ()
#26 0x08050d4f in xre_main ()
#27 0x08050d4f in xre_main ()
#28 0x0804c573 in main ()
linux, printing to file
firefox 1.0_fi-FI crashes, TB2416608M
trunk firefox-opt_2004-12-07-14Z wfm, does not crash.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
(In reply to comment #2)
> linux, printing to file
> firefox 1.0_fi-FI crashes, TB2416608M
> trunk firefox-opt_2004-12-07-14Z wfm, does not crash.

Since the trunk builds are presumably post aviary merge & the next firefox point
release is scheduled for next March, setting this bug as "RESOLVED, WFM" seems a
little enthusiastic. Shouldn't it be a 1.0 branch bug?

I've marked it as such. If you feel this is inappropriate then do change it back
(with an explanation please!) :)


Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Version: unspecified → 1.0 Branch
Well... I'd wager this is not quite serious enough to be 1.0.1 fodder, but as I
don't have a guideline to quote, I'll leave it as is.
probably dup: bug 242178
Keywords: crash
Fair enough.

cheers, Phil
The branch gets only security and other very important fixes. 
Such a single crash will not be fixed in the branch

-> wfm
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
this also occurs with one of the BFT printing tests, while trying to print
http://www.cnnsi.com/ --note that while this is still a problem with ffox 1.0
(and 1.0.1 nightly builds), this is no longer a problem with a trunk build-- at
least with 20050214-trunk ffox bits.

vrfy w4m.

BFT print test reference:
http://testrunner.mozilla.org/test.cgi?run_id=892#858
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.