On Mon, Mar 7, 2016 at 5:26 PM, Han Zhou wrote:
>
>
> On Mon, Mar 7, 2016 at 3:44 PM, Andy Zhou wrote:
> >
> > When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still
> > holds a reference count to the monitors 'changes' indexed with
> > 'unflushed' transaction id. The bug is that t
> When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still
> holds a reference count to the monitors 'changes' indexed with
> 'unflushed' transaction id. The bug is that the reference count was
> not decremented as it should in the code path.
>
> The bug caused 'changes' that have been
On Mon, Mar 7, 2016 at 3:44 PM, Andy Zhou wrote:
>
> When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still
> holds a reference count to the monitors 'changes' indexed with
> 'unflushed' transaction id. The bug is that the reference count was
> not decremented as it should in the cod
When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still
holds a reference count to the monitors 'changes' indexed with
'unflushed' transaction id. The bug is that the reference count was
not decremented as it should in the code path.
The bug caused 'changes' that have been flushed to
