Red Hat Bugzilla – Bug 1023668
ne_sock_exit() and tls thread safety
Last modified: 2013-12-13 22:53:39 EST
Created attachment 816441 [details]
init the neon library one time only
mirall systematically crashes in ne_sock_exit(), when 1/ an owncloud folder is currently updated 2/ the owncloud server uses ssl 3/ and the settings window is open (with the info window displaying the sync protocol live).
According to http://www.webdav.org/neon/doc/html/refsockinit.html, it is unsafe to unload neon, when using gnutls, but it seems to me that it's what happens each time a call to owncloud_commit() is made.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffbb0fd700 (LWP 756)]
__GI___libc_free (mem=0x25) at malloc.c:2892
2892 if (chunk_is_mmapped(p)) /* release mmapped memory. */
#0 __GI___libc_free (mem=0x25) at malloc.c:2892
#1 0x00007fffd1dc0f0a in mp_clear_multi (a=a@entry=0x7fffac0caec0)
#2 0x00007fffd1dc250a in ecc_del_point (p=0x7fffac0caec0) at ecc_points.c:62
#3 0x00007fffd1dc1b7a in _ecc_wmnaf_cache_entry_free (p=<optimized out>)
#4 ecc_wmnaf_cache_free () at ecc_mulmod_cached.c:70
#5 0x00007fffd1dc0805 in gnutls_crypto_deinit () at init.c:44
#6 0x00007fffd1d2c7e1 in gnutls_global_deinit () at gnutls_global.c:304
#7 0x00007fffd828c444 in owncloud_commit ()
#8 0x00007ffff329306c in csync_commit (ctx=0xb2c210)
#9 0x00007ffff3500016 in Mirall::CSyncRunScopeHelper::~CSyncRunScopeHelper()
() from /lib64/libowncloudsync.so.0
#10 0x00007ffff34ff98a in Mirall::CSyncThread::startSync() ()
#11 0x00007ffff351d07c in Mirall::CSyncThread::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libowncloudsync.so.0
owncloud-csync-0.90.4-1.fc19,mirall-1.4.2-1.fc19 has been submitted as an update for Fedora 19.
owncloud-csync-0.90.4-1.fc18,mirall-1.4.2-1.fc18 has been submitted as an update for Fedora 18.
owncloud-csync-0.90.4-1.fc20,mirall-1.4.2-1.fc20 has been submitted as an update for Fedora 20.
This bug still concerns version 0.90.4
Updated the updates description to leave out this bugs.
I am putting this info in a recent bug report.
mirall-1.4.2-3.fc19 has been submitted as an update for Fedora 19.
mirall-1.4.2-3.fc18 has been submitted as an update for Fedora 18.
mirall-1.4.2-3.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mirall-1.4.2-3.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mirall-1.4.2-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mirall-1.4.2-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mirall-1.4.2-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.