http://bugzilla.opensuse.org/show_bug.cgi?id=1107197 http://bugzilla.opensuse.org/show_bug.cgi?id=1107197#c15 Martin Wilck <martin.wilck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://bugzilla.gnome.org/ | |show_bug.cgi?id=797136 --- Comment #15 from Martin Wilck <martin.wilck@suse.com> --- I've filed a bug upstream, as we have only very few very harmless patches for NM in factory. https://bugzilla.gnome.org/show_bug.cgi?id=797136 On comment 13: All but the last trace shows libcurl4-internal callbacks accessing data freed in nm_connectivity_check_cancel(). The last one also occurs in a libcurl callback related to connectivity checking, but accesses a block freed elsewhere. That kind-of confirms my suspicion from comment 8 - the new asynchronous connectivity checking code seems to be susceptible to race conditions, in particular if nm_connectivity_check_cancel() is called. Unfortunately I've no time to dig into that deeper now. -- You are receiving this mail because: You are on the CC list for the bug.