You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mr TheSegfault (JIRA)" <ji...@apache.org> on 2019/07/31 20:09:00 UTC

[jira] [Comment Edited] (MINIFICPP-990) Segfault on SIGINT after shutdown initiated

    [ https://issues.apache.org/jira/browse/MINIFICPP-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897484#comment-16897484 ] 

Mr TheSegfault edited comment on MINIFICPP-990 at 7/31/19 8:08 PM:
-------------------------------------------------------------------

Thanks for debugging. I always assumed the issue is that we wait on the sem, close it then unlink it before unloading flow controller, meaning when we sem_post, the semaphore won't exist. We should likely move those sem close and sem unlink after "MiNiFi exit"  – but I haven't actually debugged it myself. I always made a mental note to "look into it" but never did. I see it a lot when I'm waiting for the repos to clear out and get impatient ( hitting ctrl+c multiple times)....so this could potentially cause data loss.


was (Author: phrocker):
Thanks for debugging. I always assumed the issue is that we wait on the sem, close it then unlink it before unloading flow controller, meaning when we sem_post, the semaphore won't exist. We should likely move those sem close and sem unlink after "MiNiFi exit"  – but I haven't actually debugged it myself. I always made a mental note to "look into it" but never did.

> Segfault on SIGINT after shutdown initiated 
> --------------------------------------------
>
>                 Key: MINIFICPP-990
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-990
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Bug
>            Reporter: Andrew Christianson
>            Priority: Major
>             Fix For: 0.7.0
>
>
> If I send a SIGINT (ctrl-c) to MiNiFI, MiNiFi begins shutdown. If I send another SIGINT while that shutdown is in progress, MiNiFi crashes with a segfault.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)