-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
large pull sometimes segfaults in g_mutex_lock(<some invalid pointer>) #601
Comments
Might be related to #383 Though I haven't re-verified whether the libsoup patch there is still necessary. |
Here's a better backtrace, from Debian unstable (GLib 2.50.2 and libsoup 2.56.0):
I had hoped that I was running with a locally-built GLib and libsoup with -Og -g, but apparently not :-( I'll try to reproduce this with locally-built libraries so I can try the patches from https://bugzilla.gnome.org/show_bug.cgi?id=768567. |
It seems I can reliably reproduce this with a locally-built GLib, libsoup and ostree master by running several
(On my laptop it has failed in or before iteration 3 every time so far, with either this, #605 or #583.) |
Can you reproduce this with one of the sanitizers, particularly |
Sadly no, I just get it to hang (#605 or similar). |
With asan, and without the patches from libsoup, I can repro this very quickly (no need to use -j and spam all the pull tests as fast as possible):
|
So I think we can safely say that the libsoup patches are an improvement. This makes me wonder whether the times I thought I reproduced this with the libsoup patches, but without asan, were PEBKAC. |
IME when using asan I had to rebuild dependent libraries (mostly glib) with |
This has not recurred on ci.debian.net since I landed the libsoup patches, so I think we can consider it closed NOTOURBUG. |
This would be more likely to tickle things like ostreedev#601 reliably. Also, while working on the curl backend, I hit on the fact that curl doesn't queue (by default, you can enable) and will happily create 20000+ concurrent TCP connections if you try. Having this test would have made that more likely to fail.
This would be more likely to tickle things like #601 reliably. Also, while working on the curl backend, I hit on the fact that curl doesn't queue (by default, you can enable) and will happily create 20000+ concurrent TCP connections if you try. Having this test would have made that more likely to fail. Closes: #650 Approved by: giuseppe
This is on Debian stable with backports: currently GLib 2.42, ostree 2016.13, flatpak 0.6.13, libsoup 2.48.
A large pull (downloading new Flatpak runtimes) sometimes segfaults. I was able to get this backtrace:
(Sorry, currently no debug symbols on the test system for libsoup or ostree - I'll try a rebuild with debug symbols when I have more time to investigate.)
Thread 5 is the one segfaulting. The mutex being a pointer to totally the wrong thing might be optimization noise, or it might indicate a use-after-free?
The text was updated successfully, but these errors were encountered: