Closed Bug 107336 Opened 23 years ago Closed 23 years ago

crash after 2nd login

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tiredguy, Assigned: joe.chou)

References

()

Details

(Keywords: crash, stackwanted)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:0.9.5) Gecko/20011012 BuildID: 2001101202 if I login to spinchat (also http://www.spinchat.com) the applet works, but after I logged out and try to login again, the applet crashes mozilla completely Reproducible: Always Steps to Reproduce: 1. Log in to Spinchat (www.spinchat.com / .de) 2. Wait until the applet has started 3. Log out 4. Log in again without restarting mozilla 5. wait until the applet starts Actual Results: mozilla crashes Expected Results: the applet should start and I should be able to use the chat the spinchat.de-admin told me this could be because of an error in "LiveConnect" (sorry, don't know what this means.) I can fix this by quitting mozilla after having logged out and restarting it.
crashers are -per definition- critical
Severity: minor → critical
Keywords: crash
Reporter: Please try a more recent talkback-enabled build: http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu-sea.tar.gz (as always, be sure to delete your old Mozilla directory before installing the new one) Then, if you get a crash, please post the Talkback ID here. (you can get the talkback id by running 'talkback' in <moz-dir>/bin/components/talkback)
Keywords: stackwanted
->OJI
Assignee: asa → joe.chou
Component: Browser-General → OJI
QA Contact: doronr → pmac
no crash for me with recent build and jre1.3.1 on redhat 6.2. Applet loads and starts ok. However, i get following exception in java console (i think this is because i am behind of proxy): java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120) at java.net.Socket.<init>(Socket.java:273) at java.net.Socket.<init>(Socket.java:100) at royal2.Client.h([DashoPro-V1.2-120198]) at royal2.Client.i([DashoPro-V1.2-120198]) at royal2.Client.start([DashoPro-V1.2-120198]) at sun.applet.AppletPanel.run(AppletPanel.java:358) at sun.plugin.navig.motif.MotifAppletViewer.maf_run(MotifAppletViewer.java:127) at sun.plugin.navig.motif.MotifAppletViewer.run(MotifAppletViewer.java:123) at java.lang.Thread.run(Thread.java:484) Reporter: please try more recent build. Please open java console before logging in, set trace level to 5 and watch what is different on second login. Please post here the output from java console - withouth your assistance we will not be able to fix this bug.
I tried on both windows 98 and linux rehat 6.2 (2002-01-28-06-trunk), it worked fine without crashing though.
This bug is related to 113957
Blocks: 113957
Bug 113957 (mentioned in comment 113957) was marked as WORKSFORME. Have anybody seen crash on this bug in latest nightbuilds or should this bug also be marked as WORKSFORME?
i just tried this with linux trunk 2002040422 with jre 1.3.1 and it worksforme. reporter, can you reproduce with a newer build?
Reporter (Thomas Bächler), please can you check to see whether this bug is still present in a recent build (Moz1-RC1 or a new nightly build). If this bug does not occur please can you resolve it worksforme.
WFM with: Mozilla Build 20002042610 SuSE Linux 7.2/glibc 2.2.2 Java2 SDK 1.4.0 (plugin installed by symlink)
No response by reporter in a month -> WFM. pi
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Chris Petersen is a new QA contact for oji component. His email is: petersen@netscape.com
Assignee: joe.chou → petersen
fixing small error for pmac@netscape.com (filter with : SPAMMAILSUCKS)
Assignee: petersen → joe.chou
QA Contact: pmac → petersen
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.