[Bug 204426] Processes terminating cannot access memory

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Jun 21 00:20:18 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426

--- Comment #114 from Robert Blayzor <rblayzor at inoc.net> ---
Even with the suggested patch, now seeing processes occasionally hang in state:

dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  0  120 sleep   vmf_de
dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  1  120 sleep   vmf_de
dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de
dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de
dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  3  120 sleep   vmf_de
dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de
dev at mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de



When this happens we usually end up with a process that leaves a lot of
detached sockets stuck in a CLOSED state. The process normally becomes
unkillable and only a reboot clears the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-threads mailing list