JDK-6185342 : java web start hangs on some solaris sparc machine
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: solaris_10,1.4.2_07,5.0u1
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9,solaris_10
  • CPU: generic,sparc
  • Submitted: 2004-10-27
  • Updated: 2012-10-09
  • Resolved: 2004-11-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
1.4.2_07 b02Fixed 6Fixed
Related Reports
Duplicate :  
JDK-6235115 - javaws needs 2 GB of memory to launch
Duplicate :  
JDK-6192694 - javaws occasionally hangs on execution
Description
the problem got exposed by the fix of  "6175681: 1.4.2 java web start sandbox application can have all permissions" exposed a problem, which on some sparc machines, running "javaws" will just hang there.   It is due to a problem in our native code, where we try to do a malloc on a undefined value, which in this case it will causes it to malloc a very huge memory space, and caused fork to fail later with ENOMEM.  This code was there since 1.4.2, but the problem never got exposed.
###@###.### 10/27/04 18:17 GMT
Comments
EVALUATION fix in 1.4.2_07 ###@###.### 10/27/04 18:18 GMT
27-10-2004
SUGGESTED FIX A simple fix for this problem is to make sure we malloc on a well defined value: (make sure stat succeed before using values returned from stat) http://web-east.east/deployment/www/webrevs/ngthomas/6175681/webrev-util/webrev/ ###@###.### 10/27/04 18:17 GMT
27-10-2004