Closed Bug 26947 Opened 26 years ago Closed 26 years ago

viewer won't start on Linux

Categories

(Core Graveyard :: Viewer App, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: pavlov)

Details

(Whiteboard: [PDT+])

DESCRIPTION: In the past few days, viewer has regressed so that it will not start on Linux. I reported this on mozilla-builds on Sunday evening, and Bryan Ryner reported it on Monday evening. My build is from Sunday morning (11:45AM PDT). STEPS TO REPRODUCE: * In debug build, run ./mozilla-viewer.sh ACTUAL RESULTS: It starts to run, and then crashes: david@dbaron ~/mozilla/src/mozilla/dist/bin > ./mozilla-viewer.sh -g MOZILLA_FIVE_HOME=/home/david/mozilla/src/mozilla/dist/bin LD_LIBRARY_PATH=/home/david/mozilla/src/mozilla/dist/bin SHLIB_PATH=/home/david/mozilla/src/mozilla/dist/bin LIBPATH=/home/david/mozilla/src/mozilla/dist/bin MOZ_PROGRAM=./viewer MOZ_TOOLKIT= moz_debug=1 moz_debugger= /usr/bin/gdb ./viewer GNU gdb 4.17.0.11 with Linux support Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (gdb) prun Breakpoint 1 at 0x807554c: file nsGtkMain.cpp, line 155. main (argc=1, argv=0xbffff8b4) at nsGtkMain.cpp:155 155 nsresult rv = NS_InitXPCOM(nsnull, nsnull); nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) nsUnixToolkitService: Using 'gtk' for the Widget Toolkit. nsUnixToolkitService: Using 'gtk' for the Gfx Toolkit. NS_SetupRegistry() MOZ_TOOLKIT=gtk, WIDGET_DLL=libwidget_gtk.so, GFX_DLL=libgfx_gtk.so [New Thread 4146] [New Thread 4137] [New Thread 4147] [New Thread 4148] [Switching to Thread 4148] [Switching to Thread 4137] Unable to instantiate Cookie Manager Going to create the event queue Program received signal SIGSEGV, Segmentation fault. 0x40380322 in ?? () from /usr/lib/libgdk-1.2.so.0 (gdb) shar ... [snip] (gdb) bt #0 0x40380322 in gdk_init_check () #1 0x402e1326 in gtk_init_check () #2 0x402e172d in gtk_init () #3 0x4074a453 in nsAppShell::Create (this=0x80e4fe0, bac=0xbffff854, bav=0xbffff8b4) at nsAppShell.cpp:212 #4 0x806d4e8 in nsViewerApp::Initialize (this=0x80bf928, argc=1, argv=0xbffff8b4) at nsViewerApp.cpp:343 #5 0x80755f1 in main (argc=1, argv=0xbffff8b4) at nsGtkMain.cpp:165 #6 0x4051fcb3 in ?? () from /lib/libc.so.6 EXPECTED RESULTS: * no crash
Waqar: Here's a bug to back up the viewer problems we discussed today. I'm also putting this on PDT radar because busting the viewer is really REALLY lame.
Assignee: rickg → waqar
Keywords: beta1
should we rewrite viewer or fix it?
Status: NEW → ASSIGNED
People have expressed interest in rewriting viewer to be more of an embedded example. However, I'll take a look at this.
Assignee: waqar → blizzard
Status: ASSIGNED → NEW
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
I agree viewer not working on Linux sucks, but we would hold a beta because something we arn't shipping doesn't work? Removing PDT+ for reconsideration.
Whiteboard: [PDT+]
Pavlov: having a working viewer is ABSOLUTELY essential for the gecko team to continue to make progress. PDT+ is perfectly valid here.
Whiteboard: [PDT+]
why is mozilla not a good enough test bed for seeing how layout works in mozilla? i don't see how not having viewer interferes with shipping the mozilla binary.
Viewer has *tons* of debugging features that are *essential* for working in layout. I wanted to fix bug 26998 last night, but I couldn't because I couldn't dump the content tree or frame tree to get a rough idea of where the problem could be. I didn't know where to start. I have even found some of these features useful for doing QA on layout.
This has nothing to do with beta1 as a product. I'm so not worried about this for beta. True, it's useful for debugging but that has nothing to do with Netscape-the-beta.
I have a viewer-alive-test ready to put on tinderbox if/when this gets fixed. My test tinderbox turns orange now because viewer doesn't start.
I have a fix. I will check in when the tree opens.
Assignee: blizzard → pavlov
targetting M14
Target Milestone: M14
fixed
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Marking Verified per last comment. Reopen if it breask again :-)
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.