274341 - crash on gutetaten.de [@ nsBlockFrame::AppendFrames]

Status: VERIFIED FIXED

(SeaMonkey :: General, defect)

Description

[Sven Krohlas]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041212
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041212

crash on gutetaten.de

Reproducible: Always
Steps to Reproduce:
1. go to http://gutetaten.de
2. click on the button "Zur Taten-Übersicht..."


Actual Results:  
Mozilla crashed

Expected Results:  
no crash

TB2506609K

Comment 1

[simon annear]

is there an easy way to find and reference a specific talkback event that is the
result of a crash.  Hopefully the following should be enough to find my talkback
crash results

running win xp so could someone change the OS from linux to all....

Application Information

 Application Launch Time
   13/12/2004 12:08 p.m.

 Build Identifier
   2004120804

 Deployment Identifier
   MozillaOrgMozillaTrunkWin322004120804

 Interface Version
            8 (0x00000008)

 Monitor Configuration Version
            1 (0x00000001)

 Platform Identifier
   Win32

 Product Identifier
   MozillaTrunk

 Talkback Configuration Version
            1 (0x00000001)

 Talkback Library Version
            7 (0x00000007)

 Vendor Identifier
   MozillaOrg

Runtime Information

 Active Application
          584 (0x00000248)

 Command Line
   "C:\Program Files\mozilla.org\Mozilla\mozilla.exe" 

 Contents of the Stack

[   0] 10 00 00 00 00 10 00 00 5D 8B EC 8B 00 10 00 80 [........].......]

 Current User Name
   sannear

Comment 2

[Hermann Schwab]

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a6) Gecko/20041212

http://gutetaten.de/vguall.htm is the page crashing Mozilla.
Look at it using view-source:http://gutetaten.de/vguall.htm

Re comment 1:
> is there an easy way to find and reference a specific talkback event?

http://talkback-public.mozilla.org/talkback/fastfind.jsp

When a talkback report is sent, a TalkbackID is sent back to Mozilla. You can
find it starting talkback.exe in the Components directory.

Before sending a report, it is useful to put the url into the URL field, and
write a small comment, maybe mentioning the bug number, if a bug is already filed.

In fastfind you can search for URLs in the URL field, or URLS or text in the
comment field. You can´t search for email addresses, so noc chance to find a
report because a mail address was filled in.
When you find your report, you see a stack signature.
You can search for this to find similar crashes, maybe bugs already filed on this.


http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB2506609K
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB2508573Z
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB2508685G

Comment 3

[Hermann Schwab]

regressed:
BuildID 2004100605 working
BuildID 2004100906 crashing

No crashes if JS is disabled.
checkins in that timeframe:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2004-10-06+04%3A00&maxdate=2004-10-09+07%3A00&cvsroot=%2Fcvsroot

Comment 4

[Mats Palmgren (inactive)]

With a printf in nsBlockFrame::DoRemoveFrame I see:
OOPS next-in-flow on same line...

This was fixed by 268119.  Please verify with a Windows build newer than
2004-12-12 10:15 PDT.

-> FIXED

Comment 5

[Sven Krohlas]

ok, it's working now with
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041213