Firefox/epiphany/galeon all crash
Kurt Buff
kurt.buff at gmail.com
Tue Jul 8 23:58:16 UTC 2008
As soon as I log into my gmail account, and several other sites.
Running 7-STABLE, amd64 - FF is 2.0.0.14, gecko is 20080628. I'm
writing this on my really old Windows laptop
Below are the last few lines from a representative set of output from
session launched from the commandline. Is it flash, or something else,
and is there anything I can do to fix this? Oddly enough, it's not
crashing on the OWA (Outlook Web Access) from my company's Exchange
server - but that's just a lot of javascript, AFAICT.
CSS Error (https://mail.google.com/mail/?ui=2&view=bsp&ver=1qygpcgurkovy
:0.16): Error in parsing value for property 'width'. Declaration
dropped.
###!!! ASSERTION: bad width: 'metrics.width>=0', file
nsLineLayout.cpp, line 1068
Break: at file nsLineLayout.cpp, line 1068
++DOMWINDOW == 17
WARNING: Moving XPConnect wrappedNative to new scope, but can't fixup
__proto__, file xpcwrappednative.cpp, line 1108
For application/x-shockwave-flash found plugin
/usr/local/lib/browser_plugins/libnpflash.so
LoadPlugin() /usr/local/lib/browser_plugins/libnpflash.so returned 29e4d60
NP_Initialize
New
nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0
nsPluginNativeWindowGtk2: call SetWindow with xid=0x2001584
About to create new ws_info...
About to create new xtbin of 100 X 100 from 0x192ccc0...
About to show xtbin(0x7b2e90)...
completed gtk_widget_show(0x7b2e90)
SetWindow
nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0
nsPluginNativeWindowGtk2: call SetWindow with xid=0x2001584
SetWindow
nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0
nsPluginNativeWindowGtk2: call SetWindow with xid=0x2001584
SetWindow
NewStream
WriteReady
Write
decoding...
The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadImplementation (server does not implement operation)'.
(Details: serial 36 error_code 17 request_code 146 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
nsStringStats
=> mAllocCount: 47580
=> mReallocCount: 7348
=> mFreeCount: 40084 -- LEAKED 7496 !!!
=> mShareCount: 29791
=> mAdoptCount: 4257
=> mAdoptFreeCount: 4072 -- LEAKED 185 !!!
More information about the freebsd-questions
mailing list