310883 - Page crashes browser while still loading

Status: RESOLVED DUPLICATE of bug 309706

(Core Graveyard :: Java: OJI, defect)

Description

[Matti]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051001 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051001 SeaMonkey/1.1a

I have no idea why.

Reproducible: Always

Comment 1

[Andrew Schultz]

worksforme with linux seamonkey trunk 2005100205.
always include a talkback ID or a stack when reporting a crash bug.

Comment 2

[Ronald Tilby]

Confirming crash.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051002
Firefox/1.6a1
Talkback ID: TB10084557X

Comment 3

[Andrew Schultz]

==> Java based on stack

Comment 4

[Hermann Schwab]

crash: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051001 Firefox/1.6a1
Java(TM) 2 Platform Standard Edition 5.0 Update 5
Talkback ID: TB10113047M

crashed when Java was enabled, loaded normally when Java was disabled.
When reporting crashes on pages using Java, please also report the version of
Java used, see Help->about Plug-ins.

There are tons of bugs with signature jpinscp.dll + 0xaa87.
Another URL mentioned often was http://www.mthoodrr.com/ but I didn't crash there.

Comment 5

[Hermann Schwab]

Bug 309706  	stack overflow crash [@ jpinscp.dll + 0xaa87]

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

Comment 6

[Matti]

(In reply to comment #1)
> worksforme with linux seamonkey trunk 2005100205.
> always include a talkback ID or a stack when reporting a crash bug.

Where do I get those data from?

Comment 7

[Hermann Schwab]

(In reply to comment #6)
> > always include a talkback ID or a stack when reporting a crash bug.
> 
> Where do I get those data from?

1. Talkback must be installed and must have sent a report. It would be fine if
you put the URL into the URL field or comment field of the record. 

2. When the report was sent successfully, a TalkbackID is sent back. open
talkback.exe in the \components directory and copy and paste the TBID from there.

3. If you are interested in the code where it crashed, use
http://talkback-public.mozilla.org/talkback/fastfind.jsp
to look at your crash:

3a: Insert the Talkback Incident ID into the Fastfind Searchfield and press GO.

3b: Search for the stack signatur you found in 3a  to find similar
bugs/URLs/reports. Most reports don't have URL and User comments, some have.
Don't use an @ in the comment field, because then the comment wouldn't be shown.
Guess the tool prevents email adresses in the comment field to be shown by
blocking the full comment.

4. if you want to place the TalkbackId into a bugzilla report, use the full form
like TB10084557X or copy from the Talkback record title like Incident ID:
10113047. If you simply write Talkback ID 10084557 or TB10084557 you don't get a
link.