After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 388698 - crash in Epiphany: closed the print preview
crash in Epiphany: closed the print preview
Status: RESOLVED DUPLICATE of bug 356632
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
: 402480 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-22 18:12 UTC by Stefan Sauer (gstreamer, gtkdoc dev)
Modified: 2007-01-31 09:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Stefan Sauer (gstreamer, gtkdoc dev) 2006-12-22 18:12:14 UTC
Version: 2.16.1

What were you doing when the application crashed?
closed the print preview


Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 165539840 vsize: 0 resident: 165539840 share: 0 rss: 18808832 rss_rlim: 0
CPU usage: start_time: 1166810441 rtime: 0 utime: 1222 stime: 0 cutime:1173 cstime: 0 timeout: 49 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1245456688 (LWP 8553)]
[New Thread -1309475952 (LWP 8562)]
[New Thread -1317868656 (LWP 8561)]
[New Thread -1292690544 (LWP 8555)]
[New Thread -1281651824 (LWP 8554)]
0xb7eff410 in ?? ()

Comment 1 Reinout van Schouwen 2006-12-23 17:13:48 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Diego Escalante Urrelo (not reading bugmail) 2007-01-28 17:11:48 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2007-01-29 18:25:55 UTC
I've installed all sort of debug packages, but still have a quite limited stacktrace. Sofar I installed debuginfo packages for glibc, glib, epiphany, xulrunner, nspr, libgnomeprint, ... (basically all libs I could guess from ldd output).


Backtrace was generated from '/opt/gnome/bin/epiphany'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1245387056 (LWP 18133)]
[New Thread -1289978992 (LWP 18135)]
[New Thread -1280984176 (LWP 18134)]
0xb7f10410 in ?? ()

Comment 4 Christian Persch 2007-01-29 18:56:31 UTC
Possibly bug 356632 ...

Maybe you can get a better trace by running epiphany under gdb, instead of just attaching it after the crash ?
Comment 5 Stefan Sauer (gstreamer, gtkdoc dev) 2007-01-29 19:13:13 UTC
gdb --args /opt/gnome/bin/epiphany --disable-crash-dialog

did the trick. Now this doesn't really look like its epiphany to blame. Any idea?

(gdb) bt
  • #0 FcCharSetDestroy
    from /usr/lib/libfontconfig.so.1
  • #1 ~nsFontMetricsPS
    at nsFontMetricsPS.cpp line 111
  • #2 nsFontMetricsPS::Release
    at nsFontMetricsPS.cpp line 135
  • #3 nsFontCache::Flush
    at nsDeviceContext.cpp line 715
  • #4 ~nsFontCache
    at nsDeviceContext.cpp line 580
  • #5 ~nsFontCachePS
    at nsDeviceContextPS.cpp line 547
  • #6 ~DeviceContextImpl
    at nsDeviceContext.cpp line 88
  • #7 ~nsDeviceContextPS
    at nsDeviceContextPS.cpp line 134
  • #8 DeviceContextImpl::Release
    at nsDeviceContext.cpp line 54
  • #9 nsDeviceContextPS::Release
    at nsDeviceContextPS.cpp line 179
  • #10 ~nsCOMPtr_base
    at nsCOMPtr.cpp line 81
  • #11 ~nsCOMPtr
    at ../../../dist/include/xpcom/nsCOMPtr.h line 542
  • #12 ~nsPrintData
    at nsPrintData.cpp line 159
  • #13 nsPrintEngine::Destroy
    at nsPrintEngine.cpp line 284
  • #14 DocumentViewerImpl::OnDonePrinting
    at nsDocumentViewer.cpp line 4243
  • #15 HandlePLEvent
    at nsPrintEngine.cpp line 4552
  • #16 PL_HandleEvent
    at plevent.c line 688
  • #17 PL_ProcessPendingEvents
    at plevent.c line 623
  • #18 nsEventQueueImpl::ProcessPendingEvents
    at nsEventQueue.cpp line 417
  • #19 event_processor_callback
    at nsAppShell.cpp line 67
  • #20 g_io_unix_dispatch
    at giounix.c line 162
  • #21 g_main_context_dispatch
    at gmain.c line 2045
  • #22 g_main_context_iterate
    at gmain.c line 2677
  • #23 g_main_loop_run
    at gmain.c line 2881
  • #24 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #25 main
    at ephy-main.c line 716

Comment 6 Christian Persch 2007-01-29 19:21:24 UTC
Gecko bug with new fontconfig versions. Seems like suse doesn't ship the fix in its gecko package.

*** This bug has been marked as a duplicate of 356632 ***
Comment 7 Stefan Sauer (gstreamer, gtkdoc dev) 2007-01-29 19:33:40 UTC
Christian, thanks a lot! I have forwarded your info to opensuse:
https://bugzilla.novell.com/show_bug.cgi?id=239911
Comment 8 Christian Persch 2007-01-29 21:26:53 UTC
You could point them directly to the upstream bug,  https://bugzilla.mozilla.org/show_bug.cgi?id=294879 which is fixed in 1.8.0.8 (for which there is no xulrunner release yet).
Comment 9 Stefan Sauer (gstreamer, gtkdoc dev) 2007-01-31 09:52:02 UTC
*** Bug 402480 has been marked as a duplicate of this bug. ***