Hello!
Merged. I was wondering a bit about the OBEX event leak (m_obexEvent):
The solution is to check explictly whether m_obexEvent already wraps a
resource
before assigning a new value to it.
Setting a new value for m_obexEvent, one of our cxxptr smart pointers,
will automatically free any existing resource pointed to by it. Why was
it possible to leak something owed by it?
Or does the commit fix the problem that the event was kept around too
long?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
