141229 - crash while i surfed through the web not specifc somtimes the browser crashs somtimes not. I get this error replay from it: xpm" line 197 Segmentation fault

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect)

Description

[Simon Schwarz]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020412
Debian/0.9.9-6
BuildID:    20020412


The Browser crashs with the output:
xpm" line 197
Segmentation fault

If xmms is running it crashs too with the output "Segmentation fault". But the
Browser crashs if xmms is not running, too.
I don't know why I've tried to find a sence in the crashes but  i've found nothing. 

Please forgive if i've made errors  my native language is not english.

I hope you can fix this bug with these informations if not write me the
questions you have to: [e-mail]

THX for this realy good broser
Simon

Reproducible: Sometimes
Steps to Reproduce:
I've tried to find a sure procedure to reproduce the crash but i can't finde
one. The onlyest thing i can say the crash come but when...

Actual Results:  If the broser crashs somtimes xmms crashs, too. And i become
this error message:
xpm" line 197
Segmentation fault


Expected Results:  running

My Hardware:
CPU: VIA C3 933 Mhz
RAM: SDRAM 512 MB (2x 256) infineon
Motherboard: MS-6368

Comment 1

[Andrew Schultz]

please try a later build (1.0rc1 has been released, or a nightly build)

do you have a talkback ID for the crash?  it's hard to know what's going on
without the talkback information.

Comment 2

[Simon Schwarz]

Hm while the first try to filling this form the browser crashs :(

ok here the Codes:
First Crash: TB5864452X
Second Crash: TB5864615Z

The crashes are more since i've switched to the new browser skin.

Theses crashes are while i tested the Version 1.0rc1 (ID: 20020417) (german
version) with talkback

Comment 3

[Kai Lahmann (is there, where MNG is)]

WFM with trunk 2002073022, linux. reporter (Simon Schwarz): can you reproduce
this bug with a recent build of mozilla (for example, 1.1beta)? if so, please
comment again with details. if not, please resolve this bug as WORKSFORME. thanks.

Comment 4

[Simon Schwarz]

the bug is solved in the newer Version.

Thx for the greatest Browser! ;)

Comment 5

[Paul Wyskoczka]

v

Comment 6

[Andreas Lange]

(This is an old bug, but as i found this searching for Via C3 I might as well
add some info for others here).

Note that compilers targeting i686 may produce output that the C3 can't handle.
This will lead to spurious crashes, dependent on code organization and the
specific compiler.

A VIA C3 is a compliant i686, but it lacks the _optional_ cmov instruction.
However all gcc versions currently output cmov instructions if told to go for
i686, while newer gcc3s has C3 as a cpu alternativ to avoid cmov's. 

The nightly builds (and releases, I think) are built for i686, thereby making
them unstable on a Via C3.