-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 1.0
-
Component/s: client-libs
-
1.1
-
sparc
-
solaris_2.4
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2009588 | 1.0 | Sami Shaio | P3 | Closed | Fixed | 1.0beta |
###@###.###
A pretty straightforward AWT implementation problem:
Calling certain native methods on AWT components that
have been disposed cause segmentation faults. For
example, the code:
{
Label err = new Label("",null,window,font);
err.dispose();
err.setText("This will break");
}
will cause the fault. Since there is currently no method
of determining whether a component is ``valid'', it would
be nice if this would at least just throw an exception,
rather than killing java...
A pretty straightforward AWT implementation problem:
Calling certain native methods on AWT components that
have been disposed cause segmentation faults. For
example, the code:
{
Label err = new Label("",null,window,font);
err.dispose();
err.setText("This will break");
}
will cause the fault. Since there is currently no method
of determining whether a component is ``valid'', it would
be nice if this would at least just throw an exception,
rather than killing java...
- backported by
-
JDK-2009588 fp.bugs<1592>Calling native methods on disposed awt components segfaults
-
- Closed
-