257639 - 1.7.2 crashes randomly on certain pages [@ nsInputStreamPump::OnStateStop ][@ nsHttpChannel::OnStopRequest ]

Status: VERIFIED DUPLICATE of bug 251969

(Core :: Networking: HTTP, defect)

Description

[Markus Gerstel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803

Mozilla 1.7.2 crashes when surfing around. Some pages (forums at heise.de) are
more likely to crash than others.

Reproducible: Sometimes
Steps to Reproduce:




Talkback IDs: TB680792Z, TB680788X, TB648895G, TB648878X

Comment 1

[Boris Zbarsky [:bzbarsky]]

Please don't file bugs without stack information or reliable steps to reproduce
as "NEW".

Once the talkback server comes back up, someone needs to look up those stacks...

Comment 2

[Markus Gerstel]

I used the Bugzilla helper which didn't give me a choice whether to file this
bug as new or unconfirmed.

Comment 3

[Andrew Schultz]

the first three crash in nsInputStreamPump::OnStateStop, the last in 
nsHttpChannel::OnStopRequest. see bug 241947 and bug 252328

==> networking

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

httpchannel::onstoprequest sounds like bug 251969 

Comment 5

[Oliver Fischer]

I can confirm this bug on FreeBSD 6 CURRENT. Mozilla crashs for example on
http://www.stern.de/wirtschaft/unternehmen/meldungen/index.html?id=522374&nv=ct_cb

Here is a log of Mozilla's debug messages:

...
nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0

nsPluginNativeWindowGtk2: call SetWindow with xid=0x2200bfe

nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0

nsPluginNativeWindowGtk2: call SetWindow with xid=0x2200bfe

nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0

nsPluginNativeWindowGtk2: call SetWindow with xid=0x2200bfe

Error loading URL
http://www.stern.de/wirtschaft/unternehmen/meldungen/index.html?id=522374&nv=ct_cb
: 804b0002

The program 'mozilla-bin' received an X Window System error.

This probably reflects a bug in the program.

The error was 'BadShmSeg (invalid shared segment parameter)'.

  (Details: serial 157 error_code 166 request_code 146 minor_code 2)

  (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: 41831

 => mReallocCount: 6615

 => mFreeCount: 38136

 => mShareCount: 27314

 => mAdoptCount: 4423

 => mAdoptFreeCount: 4260

Comment 6

[Oliver Fischer]

The URL I posted doesn't cause a crash. It is the next page of the article:
Here is its URL
http://www.stern.de/wirtschaft/unternehmen/meldungen/index.html?id=522374&p=2&nv=ct_cb

Comment 7

[Matthias Versen [:Matti]]

The crash in bug#5 seems to be a different one and not this one. 
(reporter OS = win32, crash in comment#5 is from an x-window errer caused by a
plugin (?) ) 

Comment 8

[Markus Gerstel]

Seems to be fixed with 1.7.5, had no crash since release.

Comment 9

[Darin Fisher]

most likely a duplicate of bug 251969 then.

*** This bug has been marked as a duplicate of 251969 ***

Comment 10

[Markus Gerstel]

Sounds reasonable