United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-6250714 : AwtObject::scheduleDelete() doesn't work upon app shutdown

Details
Type:
Bug
Submit Date:
2005-04-05
Status:
Closed
Updated Date:
2011-01-20
Project Name:
JDK
Resolved Date:
2005-06-17
Component:
client-libs
OS:
windows_xp
Sub-Component:
java.awt
CPU:
x86
Priority:
P2
Resolution:
Cannot Reproduce
Affected Versions:
6
Fixed Versions:
6

Related Reports
Relates:

Sub Tasks

Description
Say, we have a button. Then in awt_Toolkit.cpp we put some debug info to monitore WM_AWT_DISPOSE message processing. Now when we call removeNotify on the button AwtObject::scheduleDelete() sends the toolkit thread WM_AWT_DISPOSE message and the button object gets destroied properly. But when we just close our window with the button (thus exiting the application) AwtObject::scheduleDelete() sends WM_AWT_DISPOSE as usual but it doesn't reach the target that is the toolkit thread. So, the button object doesn't get destroied properly in the last case (only via system resources freeing). There is no problem with the button though, but when we deal with some specific resource it may not be destoied at all after the application exited.
###@###.### 2005-04-05 15:06:34 GMT

                                    

Comments
EVALUATION

In the fix for 6229122 deleting native AWT objects is synchronized with other actions (like AwtTextComponent::GetText). Both deleting and those actions are moved into a dedicated critical section, and that fixes this bug.

###@###.### 2005-04-06 11:40:49 GMT

As this bug is already fixed together with 6229122, I'm closing it as not reproducible.

###@###.### 2005-06-17 08:38:44 GMT
                                     
2005-04-05



Hardware and Software, Engineered to Work Together