226996 - Firebird crashes on this page, mozilla 1.5 works fine

Status: VERIFIED DUPLICATE of bug 225423

(Core Graveyard :: Java: Live Connect, defect)

Description

[Oleg Sidletskiy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031125 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031125 Firebird/0.7+

Clicking on the rul causes Mozilla Firebird to crash, but the site work fine in
Mozilla 1.5. Also it appears that the browser crashes after the site is redirected.

Reproducible: Always

Steps to Reproduce:
1.goto http://www.nerdcamp.net/
2.
3.

Actual Results:  
crash

Comment 1

[Mike Connor [:mconnor]]

what about with an equivalent Mozilla nightly?  this is probably a trunk bug..

Comment 2

[Jason Barnabe (np)]

Not Firebird-specific...

Comment 3

[Jason Barnabe (np)]

Attachment: testcase - html page

Comment 4

[Jason Barnabe (np)]

Attachment: testcase - Java class file

Comment 5

[Jason Barnabe (np)]

Attachment: Java class source

Comment 6

[Jason Barnabe (np)]

Attachment: Windows generated error log

Comment 7

[timeless]

.

Comment 8

[Jason Barnabe (np)]

Save both testcase files to the same directory and open the HTML page.

The HTML file calls the getMsg() method onLoad of the HTML body. The getMsg
should return the string "text from applet", which the HTML should put in the
input box. It works in IE, but crashes in Firebird 20031125 and Seamonkey
2003112008. I'm using JVM 1.4.2_02 and Win XP.

Comment 9

[Jason Barnabe (np)]

Redoing timeless's change... Sorry.

Comment 10

[Bill Gianopoulos [:WG9s]]

This does not crash for me with the win32 11/28 nightly.  This is most likely a
duplicate of bug 225423 which has already been fixed.

Comment 11

[Oleg Sidletskiy]

does not crash after upgrading to Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.6b) Gecko/20031128 Firebird/0.7+,

so it's a dupe

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

Comment 12

[Phil Schwartau]

Jason: can you confirm this bug is fixed in an up-to-date build? If so,
you can mark this bug "Verified", otherwise you can reopen it; thanks -

Comment 13

[Jason Barnabe (np)]

Verified.