StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHandling the cleanup of the gen_server state
primarykey
Id
5119107
data
AcceptedAnswerId
5119297
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-25T15:31:39.170
FavoriteCount
3
LastActivityDate
2017-02-28T17:38:44.790
LastEditDate
2011-02-25T18:14:32.447
LastEditorUserId
89804
OwnerUserId
89804
ParentId
0
PostTypeId
1
Score
7
ViewCount
2137
LastEditorDisplayName
text
Body
I have a <code>gen_server</code> running which it must clean up its state whenever it is stopped normally or it crash unexpectedly. The cleanup basically consists in deleting a few files. At this moment, when the <code>gen_server</code> crash or it is stopped normally, the cleanup is done in <code>terminate/2</code>. Is there any reason why <code>terminate/2</code> would not be called if the <code>gen_server</code> crash? Should be any other process monitoring the <code>gen_server</code> waiting to do the cleanup if the <code>gen_server</code> dies unexpectedly? So, the code is like this: <pre><code>terminate(normal, State) -> % Invoked when the process stops % Clean up the mess terminate(Error, State) -> % Invoked when the process crashes % Clean up the mess </code></pre> <hr> EDIT: I found this email in the official mailing list which is talking about the same thing: <a href="http://groups.google.com/group/erlang-programming/browse_thread/thread/9a1ba2d974775ce8" rel="noreferrer">http://groups.google.com/group/erlang-programming/browse_thread/thread/9a1ba2d974775ce8</a> As Adam says below, if we want to avoid to trap the exists in the <code>gen_server</code>, we could use different approaches. But if we trap the exists, <code>terminate/2</code> seems to be a safe place to do the cleanup as it always will be called. Furthermore we must handle correctly when <code>'EXIT'</code> is sent to <code>terminate/2</code> and to <code>handle_call/3</code> trying to propagate the errors correctly between workers and supervisors.
Tags
<erlang><otp>
Title
Handling the cleanup of the gen_server state
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USRicardo
UserOwnerUserId
1. USRicardo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHandling the cleanup of the gen_server state
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHandling the cleanup of the gen_server state
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POHandling the cleanup of the gen_server state
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.