[
https://issues.apache.org/jira/browse/MINIFICPP-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Szasz updated MINIFICPP-1542:
------------------------------------
Description: Connection::isWorkAvailable accesses its FlowFileQueue without
proper locking, resulting in unsynchronized access to the queue and a race
condition. I was lucky enough to get a segfault when comparing the penalty
expiration of a flow file from the top of the queue that has already been
destructed and its memory released back to the OS. (was:
Connection::isWorkAvailable accesses it FlowFileQueue without proper locking,
resulting in unsynchronized access to the queue and a race condition. I was
lucky enough to get a segfault when comparing the penalty expiration of a flow
file from the top of the queue that has already been destructed and its memory
released back to the OS.)
> Race condition in Connection::isWorkAvailable
> ---------------------------------------------
>
> Key: MINIFICPP-1542
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1542
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Marton Szasz
> Assignee: Marton Szasz
> Priority: Major
> Fix For: 0.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Connection::isWorkAvailable accesses its FlowFileQueue without proper
> locking, resulting in unsynchronized access to the queue and a race
> condition. I was lucky enough to get a segfault when comparing the penalty
> expiration of a flow file from the top of the queue that has already been
> destructed and its memory released back to the OS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
