Closed
Bug 55518
Opened 24 years ago
Closed 24 years ago
Browser hangs on AllocObject call (using OJI API tests)
Categories
(Core Graveyard :: Java: OJI, defect, P2)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: rpallath, Assigned: joe.chou)
Details
Using the PR3 JRE version on Solaris
Mozilla browser hangs on AllocObject call. Seems to be wating forever.
Seems to be stuck in waiting for a response which it never gets.
Without a fix for the above, most of OJI API tests would fail.
Test base is in dir.: modules/oji/src/tests
[ Internal SUN Bugtar ID 4375923 ]
The Java Plugin folks at SUN already are working on this bug.
For execution of the above tests refere to readme in modules/oji.tests/build
Updated Status whiteboard for tracking SUN high priority bugs
Also bumped up the priorit from P3 to P2.
Priority: P3 → P2
Whiteboard: suntrak-n6-highp
Another NOTE:, this bugs can be simulated only thru' aPI tests.
A normal user will not be able to simulate this just using the JRE, by invoking
applets.
Tried the fix with FCS version of java Plugin and Mozilla of the tip of RTM
branch on Solaris 2.7 and Win32 and Linux 6.2
Used a workaround to resolve FindClass problem. findclass expects a Classname
and returns a 'jclass' object.
Invoke java Plugin Control Panel(usually in the JRE/bin dir)
Set Java Runtime Parmeters to
-Xbootclasspath/a:<class dir>
After doing the above FindClass returned a valid jclass object which was passed
to AllocObject and which accordingly returned correct value.
Fixed.
Updated•24 years ago
|
Whiteboard: suntrak-n6-highp
Per Raju's latest test, the problem no longer exists, may have been fixed by
some other bug fix.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•