JDK-8013849 : Awt assert on Hashtable.cpp:124
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_7
  • CPU: x86
  • Submitted: 2013-05-02
  • Updated: 2015-02-02
  • Resolved: 2013-08-07
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.
7u80Fixed 8 b103Fixed
Related Reports
Duplicate :  
Relates :  
On Windows
>java -showversion -jar Notepad.jar
java version "1.8.0-ea-fastdebug"
Java(TM) SE Runtime Environment (build 1.8.0-ea-fastdebug-b86)
Java HotSpot(TM) Client VM (build 25.0-b28-fastdebug, mixed mode)

AWT Assertion Failure
value != NULL
File 'Hashtable.cpp', at line 124
GetLastError() is 0 : The operation completed successfully.

Do you want to break into the debugger?

This can be traced to 8 the earliest build.
Would be nice if this was fixed. I got bit by it again today.

In that case I agree. I usually do debug builds so didn't realize that.

This issue is reproducible only in the debug build as I know, so I suppose this should stay P4.

I encountered the same problem with 7u-dev code cloned yesterday. I encountered this using SwingSet2 and it occurred whenever pressing the tab key to move to various controls. Using the tab key to change focus is very important for users who are blind as this is the only way they can move from control to control. Due to this I think this should be at least P2 rather than a P4. I worked around the problem by replacing the DASSERT with: if (value == NULL) return NULL;

Reproducible with the latest 8 debug build.

Start Notepad application, input anything in input area by keyboard then hit the assert. This happened to all programs with input boxes in debug build.