StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2242203
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-11T04:08:26.357
FavoriteCount
0
LastActivityDate
2010-02-11T04:08:26.357
LastEditDate
LastEditorUserId
0
OwnerUserId
14731
ParentId
2231080
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I ran across the answer in this excellent blog post: <a href="http://www.pushing-pixels.org/?p=369" rel="nofollow noreferrer">http://www.pushing-pixels.org/?p=369</a> <blockquote> With the current implementation, AWT terminates all its helper threads allowing the application to exit cleanly when the following three conditions are true: <ul> <li>There are no displayable AWT or Swing components.</li> <li>There are no native events in the native event queue.</li> <li>There are no AWT events in java EventQueues.</li> </ul> </blockquote> [...] <blockquote> In the current implementation this timeout is 1000 ms (or one second). What this effectively means that AWT is not shutdown immediately after disposing the last window in your application and processing all pending events. Instead, it wakes every second, checks for any pending or processed events during the sleep and continues sleeping if there have been any such events. </blockquote> The author goes on to say that his code posts an event to the EDT every 100ms in spite of the fact that the associated Window is no longer visible. This is exactly what happens in my case as well! The ScheduledExecutorService is posting events into the EDT, which in turn prevents AWT from shutting down, which in turn means that the ScheduledExecutorService will keep on posting more events. As an aside, I am surprised by the number of people that recommend the use of <code>JFrame.EXIT_ON_CLOSE</code>. Each to his own I guess, but I recommend you read <a href="http://findbugs.sourceforge.net/bugDescriptions.html#DM_EXIT" rel="nofollow noreferrer">http://findbugs.sourceforge.net/bugDescriptions.html#DM_EXIT</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy doesn't the EDT shut down when all live threads are daemon?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGili
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy doesn't the EDT shut down when all live threads are daemon?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.