P4
FULL PRODUCT VERSION :
java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b22)
Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
FULL OS VERSION :
Microsoft Windows [Version 6.1.7600]
A DESCRIPTION OF THE PROBLEM :
If the java.exe executable was launched from a mapped drive and during operation the connection to the drive is lost, the JVM crashes during its shutdown.
The crash doesn't appear to happen when the java.exe was invoked as elevated user. So it seems there is some policy check missing....
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: No
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
In order to reproduce, any java application can be used, where the java executable (java.exe) is located on an mapped network drive, e.g. Z:\bin\java.exe
After the application has started as non-elevated process and the connection to the drive is lost or the drive was disconnected, the jvm will crash once it stops...
(I haven't tried any other OS than Windows 7.)
With -Xint the error is different, but still not working as expected.
EXPECTED VERSUS ACTUAL BEHAVIOR :
expected: the jvm stops normally (like it is doing when running elevated)
actual: the jvm shows an appcrash
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Problem Event Name: APPCRASH
Application Name: java.exe
Application Version: 0.0.0.0
Application Timestamp: 4fa226cf
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16915
Fault Module Timestamp: 4ec4b137
Exception Code: c00000fd
Exception Offset: 00000000000157cd
OS Version: 6.1.7600.2.0.0.256.28
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
can be easily reproduced with jvisualvm.....
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
make sure java.exe is located on a local directory.
java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b22)
Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
FULL OS VERSION :
Microsoft Windows [Version 6.1.7600]
A DESCRIPTION OF THE PROBLEM :
If the java.exe executable was launched from a mapped drive and during operation the connection to the drive is lost, the JVM crashes during its shutdown.
The crash doesn't appear to happen when the java.exe was invoked as elevated user. So it seems there is some policy check missing....
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: No
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
In order to reproduce, any java application can be used, where the java executable (java.exe) is located on an mapped network drive, e.g. Z:\bin\java.exe
After the application has started as non-elevated process and the connection to the drive is lost or the drive was disconnected, the jvm will crash once it stops...
(I haven't tried any other OS than Windows 7.)
With -Xint the error is different, but still not working as expected.
EXPECTED VERSUS ACTUAL BEHAVIOR :
expected: the jvm stops normally (like it is doing when running elevated)
actual: the jvm shows an appcrash
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Problem Event Name: APPCRASH
Application Name: java.exe
Application Version: 0.0.0.0
Application Timestamp: 4fa226cf
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16915
Fault Module Timestamp: 4ec4b137
Exception Code: c00000fd
Exception Offset: 00000000000157cd
OS Version: 6.1.7600.2.0.0.256.28
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
can be easily reproduced with jvisualvm.....
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
make sure java.exe is located on a local directory.