On Wed, Mar 21, 2012 at 10:31:24AM +0100, Jonas Ådahl wrote:
> Instead of directly freeing an event source upon removal put it in a
> queue later handled by the event loop; either after a dispatch or upon
> event loop destruction.
>
> This is necessary to avoid already queued up event sources to b
Instead of directly freeing an event source upon removal put it in a
queue later handled by the event loop; either after a dispatch or upon
event loop destruction.
This is necessary to avoid already queued up event sources to be freed
during some other dispatch callback, causing segmentation fault
On 03/21/2012 09:35 AM, Jonas Ådahl wrote:
> Instead of directly freeing an event source upon removal put it in a
> queue later handled by the event loop; either after a dispatch or upon
> event loop destruction.
>
> This is necessary to avoid already queued up event sources to be freed
> during s
Instead of directly freeing an event source upon removal put it in a
queue later handled by the event loop; either after a dispatch or upon
event loop destruction.
This is necessary to avoid already queued up event sources to be freed
during some other dispatch callback, causing segmentation fault
On Tue, Mar 20, 2012 at 3:40 PM, Kristian Høgsberg wrote:
> On Tue, Mar 20, 2012 at 9:21 AM, Jonas Ådahl wrote:
>> Instead of directly destroying an event source upon removal only destroy
>> it in case its event loop is not dispatching. If dispatching the event
>> source is marked for destruction
On Tue, Mar 20, 2012 at 9:21 AM, Jonas Ådahl wrote:
> Instead of directly destroying an event source upon removal only destroy
> it in case its event loop is not dispatching. If dispatching the event
> source is marked for destruction and added to the check list and
> destroyed in post_dispatch_ch
On 03/20/2012 02:21 PM, Jonas Ådahl wrote:
> Instead of directly destroying an event source upon removal only destroy
> it in case its event loop is not dispatching. If dispatching the event
> source is marked for destruction and added to the check list and
> destroyed in post_dispatch_check(); if
On 03/20/2012 03:21 PM, Jonas Ådahl wrote:
Instead of directly destroying an event source upon removal only destroy
it in case its event loop is not dispatching. If dispatching the event
source is marked for destruction and added to the check list and
destroyed in post_dispatch_check(); if not it
Instead of directly destroying an event source upon removal only destroy
it in case its event loop is not dispatching. If dispatching the event
source is marked for destruction and added to the check list and
destroyed in post_dispatch_check(); if not it is destroyed immediately.
Signed-off-by: Jo
