-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
1.1.8
-
x86
-
windows_nt
win32: theAWTToolkitWindow: java.exe - Application Error
Unhandled exception in java.exe (MSVCRT.DLL):
Access Violation
This problem appears for 1.1.8 build D and is related to changes for bug fix
for 4046769. It is observed on WinNT4.0 (SP3 or 4) with MSVCRT.DLL V6 (File
version 6.00.8267.0). It does not occur for MSVCRT.DLL V5.
The following test case demonstrates the problem. The application error pops
up when exiting the application (window close icon or Alt-F4).
import javax.swing.*;
import javax.swing.event.*;
import java.awt.*;
import java.awt.event.*;
public class TestCase extends JFrame {
public static void main (String[] argv) {
new TestCase();
}
public TestCase() {
setSize(300, 300);
setVisible(true);
addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent e) {
System.exit(0);
}
});
}
}
The problem is not observed every time, and is not specific to JFrame (although
when instead using awt.Frame in the above test case, the problem disappears).
The problem has been seen for other applications that use (non-Swing)
lightweight components.
Unhandled exception in java.exe (MSVCRT.DLL):
Access Violation
This problem appears for 1.1.8 build D and is related to changes for bug fix
for 4046769. It is observed on WinNT4.0 (SP3 or 4) with MSVCRT.DLL V6 (File
version 6.00.8267.0). It does not occur for MSVCRT.DLL V5.
The following test case demonstrates the problem. The application error pops
up when exiting the application (window close icon or Alt-F4).
import javax.swing.*;
import javax.swing.event.*;
import java.awt.*;
import java.awt.event.*;
public class TestCase extends JFrame {
public static void main (String[] argv) {
new TestCase();
}
public TestCase() {
setSize(300, 300);
setVisible(true);
addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent e) {
System.exit(0);
}
});
}
}
The problem is not observed every time, and is not specific to JFrame (although
when instead using awt.Frame in the above test case, the problem disappears).
The problem has been seen for other applications that use (non-Swing)
lightweight components.