Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2040619 | 1.4.0 | Tao Ma | P1 | Resolved | Fixed | beta2 |
JDK-2040618 | 1.3.1_01 | Tao Ma | P1 | Closed | Fixed | 01 |
JDK-2040617 | 1.3.0_04 | Tao Ma | P1 | Closed | Fixed | 04 |
JDK-2040616 | 1.2.2_09 | Tao Ma | P1 | Closed | Fixed | 09 |
One of my ISVs ships a bean that includes a Canvas, and a native 3D model viewer
widget that lays on top of the Canvas. They use JNI to communicate with their
native viewer. When they place this bean in a variety of Java components
(including Frame, JFrame, JPanel, or JSplitPane) and drag the mouse from the
Java component into the native window, the app crashes.
See the "comments" section of this bug report for stack traces from gdb and from the ISV's app, and for instructions on how to reproduce the bug.
When the crash was first noticed, the Java component was not a mouse event listener. The ISV tried to trap/handle the problem by making the component into a listener, but had no luck.
The ISV reported this crash on Solaris 8 using Java Version 1.2.2.05a.
I saw the crash on Solaris 8 using:
Solaris_JDK_1.2.2_05a
Solaris_JDK_1.2.2_06
Solaris_JDK_1.2.2_07
I can't make the crash occur on Solaris_JDK_1.2.1_04c; the app seems to run fine
on this JDK.
On JDK 1.3.0 the app crashes as soon as it starts with the following error; this
prevents me from dragging the mouse from the frame into the native widget to
reproduce the bug reported by the ISV.
# # An unexpected exception has been detected in native code outside the VM.#
Program counter=0xf3fe4ccc
#
# Problematic Thread: prio=6 tid=0x4f0200 nid=0xd runnable
#
Abort
widget that lays on top of the Canvas. They use JNI to communicate with their
native viewer. When they place this bean in a variety of Java components
(including Frame, JFrame, JPanel, or JSplitPane) and drag the mouse from the
Java component into the native window, the app crashes.
See the "comments" section of this bug report for stack traces from gdb and from the ISV's app, and for instructions on how to reproduce the bug.
When the crash was first noticed, the Java component was not a mouse event listener. The ISV tried to trap/handle the problem by making the component into a listener, but had no luck.
The ISV reported this crash on Solaris 8 using Java Version 1.2.2.05a.
I saw the crash on Solaris 8 using:
Solaris_JDK_1.2.2_05a
Solaris_JDK_1.2.2_06
Solaris_JDK_1.2.2_07
I can't make the crash occur on Solaris_JDK_1.2.1_04c; the app seems to run fine
on this JDK.
On JDK 1.3.0 the app crashes as soon as it starts with the following error; this
prevents me from dragging the mouse from the frame into the native widget to
reproduce the bug reported by the ISV.
# # An unexpected exception has been detected in native code outside the VM.#
Program counter=0xf3fe4ccc
#
# Problematic Thread: prio=6 tid=0x4f0200 nid=0xd runnable
#
Abort
- backported by
-
JDK-2040619 Java Crash When Dragging Into Native Widget
-
- Resolved
-
-
JDK-2040616 Java Crash When Dragging Into Native Widget
-
- Closed
-
-
JDK-2040617 Java Crash When Dragging Into Native Widget
-
- Closed
-
-
JDK-2040618 Java Crash When Dragging Into Native Widget
-
- Closed
-
- relates to
-
JDK-4862593 JVM crash when dragging from Java UI component to natively rendered window/peer
-
- Resolved
-