bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

seamonkey crash without error message

RESOLVED WORKSFORME

Status

SeaMonkey
General
RESOLVED WORKSFORME
6 years ago
5 years ago

People

(Reporter: Florian, Unassigned)

Tracking

SeaMonkey 2.11 Branch
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme INCO 2013-09-15)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 2012071300

Steps to reproduce:

Started Seamonkey over Start Menu, browsed in the Internet (webpage www.iwiw.hu), done some klicks on pictures or something else, used the Browser back Button often;
sometimes when the Back Button is used the Browser crashes without an errormessage.
When the browser is newly opened it is on the last page (with login)


Actual results:

sometimes when the Back Button is used the Browser crashes without an errormessage.

When the Browser is started from a commandline the following Error ist shown after the crash:
###!!! ABORT: X_CopyArea: BadDrawable (invalid Pixmap or Window parameter); 3 requests ago: file /home/abuild/rpmbuild/BUILD/seamonkey/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 190
###!!! ABORT: X_CopyArea: BadDrawable (invalid Pixmap or Window parameter); 3 requests ago: file /home/abuild/rpmbuild/BUILD/seamonkey/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 190
/usr/bin/seamonkey: Zeile 139:  4410 Speicherzugriffsfehler  $MOZ_PROGRAM "$@"



Expected results:

The Browser should not crash
(Reporter)

Comment 1

6 years ago
System:
opensuse 12.1 with all patches
Adobe FlashPlayer 11.2 browserplugin
Kernel 3.1.10-1.16-default i686
IIUC: Zeile = line; Speicherzugriffsfehler = memory access error. Hm.

You seem to have reported this bug using Firefox; but which SeaMonkey version were you using? Depending on where you got it, the "latest version" of SeaMonkey can be any of these:
- openSUSE (Update)      2.10-2.21.2-i586
- openSUSE (Update-Test) 2.11-2.24.2-i586
- Mozilla  (Release)     2.11        i686  (en-US or de?)
- Mozilla  (Beta)        2.12b2      i686  (en-US or de?)
- Mozilla  (Aurora)      2.13a2      i686  (en-US or de?) (date?)
- Mozilla  (Trunk)       2.14a1      i686  (en-US or de?) (date?)

The answer (please copy-paste it) is at the bottom of the "Help → About SeaMonkey" page, on the two lines labeled "User agent" and "Build identifier". Older versions may have only one of them. The result is probably similar to the two top lines in comment #0, but not identical, and slightly longer.

Comment 3

6 years ago
Also, if you open about:crashes, do you have any crash reports there?
(Reporter)

Comment 4

6 years ago
Hi people,

this is the first time i opened a bug :-)
Here the information:

1. Verison:
Build-Identifikator: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Firefox/14.0.1 SeaMonkey/2.11

2. about:crashes
Here i receive a message simmilar to "wrong address format" or "the address has a unknown format"

Here the about:buildconfig
Build Machine

build35
Build platform
target
i686-pc-linux-gnu
Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 4.6.2 (SUSE Linux) 	-pedantic -Wall -Wpointer-arith -Wdeclaration-after-statement -Werror=return-type -Wtype-limits -Wempty-body -Wno-unused -Wno-overlength-strings -Wcast-align -Wno-long-long -fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Os -fno-strict-aliasing -fno-strict-aliasing -ffunction-sections -fdata-sections -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer
c++ 	gcc version 4.6.2 (SUSE Linux) 	-fno-rtti -pedantic -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Wtype-limits -Wempty-body -Wno-ctor-dtor-privacy -Wno-overlength-strings -Wno-invalid-offsetof -Wno-variadic-macros -Wcast-align -Wno-long-long -fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Os -fno-strict-aliasing -fno-exceptions -fno-strict-aliasing -std=gnu++0x -ffunction-sections -fdata-sections -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer
Configure arguments

--enable-application=suite --libdir=/usr/lib/seamonkey --prefix=/usr --with-l10n-base=/home/abuild/rpmbuild/BUILD/l10n --disable-tests --enable-optimize --disable-debug --disable-dtd-debug --enable-libxul --with-system-nspr --with-system-nss --with-system-jpeg --with-system-zlib --enable-ldap-experimental --disable-installer --disable-mochitest --disable-crashreporter --enable-startup-notification --enable-system-hunspell --enable-libproxy --enable-application=suite --libdir=/usr/lib/seamonkey --prefix=/usr --with-l10n-base=/home/abuild/rpmbuild/BUILD/l10n --disable-tests --enable-optimize --disable-debug --disable-dtd-debug --enable-libxul --with-system-nspr --with-system-nss --with-system-jpeg --with-system-zlib --enable-ldap-experimental --disable-installer --disable-mochitest --disable-crashreporter --enable-startup-notification --enable-system-hunspell --enable-libproxy --enable-application=../suite --disable-official-branding --with-branding=../suite/branding/nightly --with-l10n-base=/home/abuild/rpmbuild/BUILD/l10n --cache-file=.././config.cache --srcdir=/home/abuild/rpmbuild/BUILD/seamonkey/mozilla

Comment 5

5 years ago
Do you still have this problem?
Flags: needinfo?(florianballango)
Whiteboard: closeme INCO 2013-09-15
(Reporter)

Comment 6

5 years ago
with newer Versions the Crash does not occur
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
(Reporter)

Updated

5 years ago
Flags: needinfo?(florianballango)
You need to log in before you can comment on or make changes to this bug.