Closed Bug 88333 Opened 23 years ago Closed 23 years ago

Browser Crasher - Possibly in form submission? [@ PR_AtomicDecrement]

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: kirkpp, Assigned: pollmann)

References

()

Details

(Keywords: crash, topcrash, Whiteboard: DIGBug, PDT+)

Crash Data

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2)
Gecko/20010627 Netscape6/6.1
BuildID:    2001062708

The browser crashes during an operation where our data is sent to the server. 
In at least one configuration of our application, this involves a form
submission (which we have seen to have had problems previously).  However, in
this case I haven't yet isolated it sufficiently to know which line of our
client JS code causes the browser to crash.  

I will do further work to narrow down where this crash is occurring, but in the
meantime I do have a stack trace from Talkback.

Also, the URL listed above is behind the Netscape firewall, and I may need to
change configuration on the server from time to time, so if your looking to test
of this server, we'll have to coordinate testing.

Reproducible: Always
Steps to Reproduce:
1. Go to http://kirkpp/Calendar and click the "Add Appointment Icon"
2. In the ensuing "Appointment Details Dialog", hit the save button.


Actual Results:  1. Go to http://kirkpp/Calendar and click the "Add Appointment
Icon"
2. In the ensuing "Appointment Details Dialog", hit the save button.
3. The browser crashes.

Expected Results:  1. Go to http://kirkpp/Calendar and click the "Add
Appointment Icon"
2. In the ensuing "Appointment Details Dialog", hit the save button.
3. The form submission succeeds, and the data gets to the server.

Here's the stack trace from Talkback:


Incident ID 32307134 
Stack Signature PR_AtomicDecrement 2db27efe  
Bug ID  
Trigger Time  2001-06-28 19:37:25  
User Comments   
Build ID 2001062710  
Product ID Netscape6.10  
Platform ID Win32  
Stack Trace  
PR_AtomicDecrement [../../../../pr/src/misc/pratom.c, line 292] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor' 
nsParser::Release [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line
422] 
nsXMLContentSink::~nsXMLContentSink
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
173] 
nsXMLContentSink::Release
[d:\builds\seamonkey\mozilla\content\xml\document\src\nsXMLContentSink.cpp, line
231] 
nsParser::~nsParser [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 392] 
nsParser::`scalar deleting destructor'
this one is on the embedding hot list.  it would be good if we could get
a reduced test case posted in the bug and get going on this one quickly.
Assignee: rods → pollmann
Whiteboard: DIGBug
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash
I dont see the add appointment button... I get redirected to BackDoorLogin page 
and when I put in my name I get into http://kirkpp/Signup page. If I hit refresh 
on it I crash. Is it the same crash, or a different one?
I am able to reproduce the refreshing bug on windows 98 and 2000. 
On 2000 the State pulldown menu doesnt work, but it does on 98.
On 98 the Start My Calendar doesnt work, but it does on 2000.

Steps to reproduce this crash:
1) goto http://kirkpp/Calendar, get redirected to backdoorsignin
2) put in some name for screen name click "Submit Query"
2.5 (optional)) try to pull down the State menu
3) Hit the refresh button, and wait several seconds.

For me it happens 100% of the time.
Adding cc's and changing keywords and summary for talkback tracking.
Keywords: topcrash
Summary: Browser Crasher - Possibly in form submission? → Browser Crasher - Possibly in form submission? [@ PR_AtomicDecrement]
Marking PDT+.  DIG blocker.
Whiteboard: DIGBug → DIGBug, PDT+
According to the latest Talkback data, this crash last occurred with build
2001062710 on the Netscape6.10 branch (12 incidents) and build 2001062809 on the
MozillaTrunk (1 incident).  There are no recent crashes with this stack
signature...did someone actually fix this or should we mark it worksforme? 

The crash that vladimire@netscape.com  mentions on 7/2 is actually bug 88343.  I
was able to reproduce it and the stack trace was not the same as the one logged
here, but rather the crash reported in bug 88343.

Marking worksforme for now, since I cannot crash using kirkpp's original steps
to reproduce.  I was able to create an account and save an appointment without
any problems.  Please change the resolution if this was actually fixed at some
point.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
I'm also not seeing this in any recent builds.  Thanks!
Status: RESOLVED → VERIFIED
I tried this yesterday with 7-7 0.9.2 build, and the bug was not occurring for 
me, either.  I hoping to do some further testing, but it does look like it's 
gone!
Crash Signature: [@ PR_AtomicDecrement]
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.