Page crashes browser while still loading

RESOLVED DUPLICATE of bug 309706

Status

--
critical
RESOLVED DUPLICATE of bug 309706
13 years ago
8 years ago

People

(Reporter: boofy_bloke, Assigned: yuanyi21)

Tracking

({crash})

Trunk
x86
Windows XP
crash

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
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

13 years ago
worksforme with linux seamonkey trunk 2005100205.
always include a talkback ID or a stack when reporting a crash bug.
Keywords: crash
Version: Other Branch → Trunk

Comment 2

13 years ago
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

13 years ago
==> Java based on stack
Assignee: general → yuanyi21
Component: General → Java: OJI
Product: Mozilla Application Suite → Core
QA Contact: general → pete.zha

Comment 4

13 years ago
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.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 5

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

*** This bug has been marked as a duplicate of 309706 ***
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → DUPLICATE
(Reporter)

Comment 6

13 years ago
(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

13 years ago
(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.

Updated

8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.