A DESCRIPTION OF THE REQUEST :
I am webbugs processor who mainly deals with hotspot/runtime issues submitted via (http://java.sun.com/webapps/bugreport/). I see the following crashes daily reported by many customers. The issue is that the line "Please refer to release documentation for possible reason and solutions" should be removed from the NOTE in the following type of crashes.

Sample Error Messsage:
----------------------

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x3499558
Function=[Unknown.]
Library=C:\WINDOWS\System32\YPCLSP.dll

NOTE: We are unable to locate the function name  customer  for the error
     just occurred. Please refer to release documentation for possible
     reason and solutions.


Current Java thread:
   at java.net.PlainSocketImpl.socketClose0(Native Method)
   at java.net.PlainSocketImpl.socketPreClose(Unknown Source)
   at java.net.PlainSocketImpl.close(Unknown Source)
   - locked <0x100ac708> (a java.lang.Object)
   at java.net.Socket.close(Unknown Source)
   - locked <0x100ac718> (a java.lang.Object)
   - locked <0x100a61c0> (a java.net.Socket)
   at sun.net.www.http.HttpClient.closeServer(Unknown Source)
   at sun.net.www.http.HttpClient.finished(Unknown Source)
   at sun.net.www.http.ChunkedInputStream.closeUnderlying(Unknown Source)
   at sun.net.www.http.ChunkedInputStream.processRaw(Unknown Source)
   at sun.net.www.http.ChunkedInputStream.readAheadNonBlocking(Unknown Source)
   at sun.net.www.http.ChunkedInputStream.readAhead(Unknown Source)
   at sun.net.www.http.ChunkedInputStream.available(Unknown Source)
   - locked <0x10039288> (a sun.net.www.http.ChunkedInputStream)
   at java.io.FilterInputStream.available(Unknown Source)
   at java.io.BufferedInputStream.read(Unknown Source)
   - locked <0x1003a988> (a java.io.BufferedInputStream)
   at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)
   at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)
   at sun.nio.cs.StreamDecoder.read(Unknown Source)
   - locked <0x1003b1e8> (a java.io.InputStreamReader)
   at sun.nio.cs.StreamDecoder.read0(Unknown Source)
   - locked <0x1003b1e8> (a java.io.InputStreamReader)
   at sun.nio.cs.StreamDecoder.read(Unknown Source)
   - locked <0x1003b1e8> (a java.io.InputStreamReader)
   at java.io.InputStreamReader.read(Unknown Source)
   at java.io.Reader.read(Unknown Source)
   at javax.swing.text.html.parser.Parser.readCh(Unknown Source)
   at javax.swing.text.html.parser.Parser.parse(Unknown Source)
   - locked <0x10066cc0> (a javax.swing.text.html.parser.DocumentParser)
   at javax.swing.text.html.parser.DocumentParser.parse(Unknown Source)
   at javax.swing.text.html.parser.ParserDelegator.parse(Unknown Source)
   at com.sun.javaws.ui.player.HTMLEntryManager.parseURL(Unknown Source)
   at com.sun.javaws.ui.player.HTMLEntryManager.access$000(Unknown Source)
   at com.sun.javaws.ui.player.HTMLEntryManager$1.run(Unknown Source)

Dynamic libraries:
0x00400000 - 0x00407000     C:\Program Files\Java\j2re1.4.2_01\bin\javaw.exe

#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_01-b06 mixed mode)
#

JUSTIFICATION :
The line "Please refer to release documentation for possible reason and solutions" should be removed or replaced with a more helpful message.  Customers who obey these instructions will look into the release documentation and not find any obvious description of how to resolve the error.


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
NOTE: We are unable to locate the function name  customer  for the error
     just occurred. Please refer to release documentation for possible
     reason and solutions.
ACTUAL -
The line "Please refer to release documentation for possible reason and solutions" should be removed(or should be replaced with a more helpful message)in the NOTE.
(Incident Review ID: 227818) 
======================================================================

N/A

This message no longer exists in Tiger with the fatal error handling changes.

  xxxxx@xxxxx   2003-12-01