Pausing sync causes crash #245

Burtan · 2013-01-15T14:22:19Z

Hi,
I'm using owncloud 1.2.0beta1 client with oc server 4.5.5. Both running debian wheezy.
When stoping synchronization and restarting it again, oc reproducable crashes, giving back "segmentation fault" in the terminal.

Best regards,
Burtan

woboq · 2013-01-16T19:50:47Z

Can you run it with gdb /path/to/mirall ?
Then on the crash, type bt

Burtan · 2013-01-16T20:46:38Z

owncloud won't start actually
frederik@fred-lap-deb:~$ gdb /usr/bin/owncloud GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/owncloud...(no debugging symbols found)...done. (gdb)

smessmer · 2013-01-16T21:25:24Z

You just started the gdb console and now have to type "run".
When owncloud crashed, you'll see the segfault in the gdb console and can get a stacktrace via typing "backtrace".

I think your bug report could be a duplicate of my problem: #237

Burtan · 2013-01-17T10:00:42Z

Here are my results:


frederik@fred-lap-deb:~$ gdb owncloud
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/owncloud...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/owncloud 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe468e700 (LWP 6297)]
[New Thread 0x7fffe3e8d700 (LWP 6300)]
[New Thread 0x7fffe3010700 (LWP 6301)]
[New Thread 0x7fffe280f700 (LWP 6341)]
[New Thread 0x7fffe200e700 (LWP 6344)]
[New Thread 0x7fffe180d700 (LWP 6345)]
[New Thread 0x7fffca39e700 (LWP 6346)]
[Thread 0x7fffe180d700 (LWP 6345) exited]
[Thread 0x7fffca39e700 (LWP 6346) exited]
[New Thread 0x7fffca39e700 (LWP 6387)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffca39e700 (LWP 6387)]
0x00007ffff603ac77 in csync_vio_get_error_string ()
   from /usr/lib/libocsync.so.0
(gdb) bt
#0  0x00007ffff603ac77 in csync_vio_get_error_string ()
   from /usr/lib/libocsync.so.0
#1  0x00007ffff6282ed4 in Mirall::CSyncThread::startSync() ()
   from /usr/lib/libowncloudsync.so
#2  0x00007ffff6294174 in Mirall::CSyncThread::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libowncloudsync.so
#3  0x00007ffff6639a2e in QObject::event (this=0xf16550, e=)
    at kernel/qobject.cpp:1195
#4  0x00007ffff730270c in QApplicationPrivate::notify_helper (
    this=this@entry=0x69c370, receiver=receiver@entry=0xf16550, e=e@entry=
    0xd89570) at kernel/qapplication.cpp:4556
#5  0x00007ffff7306b8a in QApplication::notify (this=0x7fffffffe210, 
    receiver=0xf16550, e=0xd89570) at kernel/qapplication.cpp:4417
#6  0x00007ffff6624b5e in QCoreApplication::notifyInternal (this=
    0x7fffffffe210, receiver=receiver@entry=0xf16550, 
    event=event@entry=0xd89570) at kernel/qcoreapplication.cpp:915
#7  0x00007ffff66289e1 in sendEvent (event=0xd89570, receiver=0xf16550)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#8  QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, 
    data=0x104c990) at kernel/qcoreapplication.cpp:1539
#9  0x00007ffff66530e3 in sendPostedEvents ()
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#10 postEventSourceDispatch (s=0x7fffb9a56770)
---Type  to continue, or q  to quit---
    at kernel/qeventdispatcher_glib.cpp:279
#11 0x00007ffff4930355 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff4930688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff4930744 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff6653276 in QEventDispatcherGlib::processEvents (this=
    0x7fffb8173520, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#15 0x00007ffff66238af in QEventLoop::processEvents (this=this@entry=
    0x7fffca39de20, flags=...) at kernel/qeventloop.cpp:149
#16 0x00007ffff6623b38 in QEventLoop::exec (this=0x7fffca39de20, flags=...)
    at kernel/qeventloop.cpp:204
#17 0x00007ffff6526d70 in QThread::exec (this=)
    at thread/qthread.cpp:501
#18 0x00007ffff6529d0b in QThreadPrivate::start (arg=0x1052a90)
    at thread/qthread_unix.cpp:307
#19 0x00007ffff4e00d9b in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#20 0x00007ffff5332b5d in clone () from /lib/x86_64-linux-gnu/libc.so.6

smessmer · 2013-01-17T12:01:15Z

It looks very similar to the issue I linked to above. That one was solved in the mean time. Did you try the solution there?

dragotin · 2013-01-17T14:03:40Z

Yes, please check if you have modules/libocsync_owncloud.so in your csync build dir.

Burtan · 2013-01-17T16:02:29Z

root@fred-lap-deb:/home/frederik# locate csync /home/frederik/.local/share/data/ownCloud/ocsync.conf /home/frederik/.local/share/data/ownCloud/ocsync_log.conf /usr/etc/ocsync /usr/etc/ocsync/ocsync.conf /usr/etc/ocsync/ocsync_exclude.conf /usr/lib/libocsync.so.0 /usr/lib/libocsync.so.0.2.0 /usr/lib/ocsync-0 /usr/lib/ocsync-0/ocsync_owncloud.so /usr/share/doc/libocsync-plugin-owncloud /usr/share/doc/libocsync0 /usr/share/doc/libocsync-plugin-owncloud/changelog.Debian.gz /usr/share/doc/libocsync0/changelog.Debian.gz /var/cache/apt/archives/libocsync-plugin-owncloud_0.70.0beta1-1_amd64.deb /var/cache/apt/archives/libocsync0_0.70.0beta1-1_amd64.deb /var/lib/dpkg/info/libocsync-plugin-owncloud.list /var/lib/dpkg/info/libocsync-plugin-owncloud.md5sums /var/lib/dpkg/info/libocsync0.list /var/lib/dpkg/info/libocsync0.md5sums /var/lib/dpkg/info/libocsync0.postinst /var/lib/dpkg/info/libocsync0.postrm /var/lib/dpkg/info/libocsync0.shlibs

there is no libocsync_owncloud.so
I will now follow the solutions described in #237

Burtan · 2013-01-17T17:15:26Z

Installing libneon27-dev did not help.

dragotin · 2013-01-17T17:18:15Z

You have to clear all build dirs and rebuild csync again.

danimo · 2013-02-06T00:56:47Z

Adjusted title. Crash on pause is a frequently reported issue. I will consollidate the bugs so we get a better overview.

danimo · 2013-02-14T16:45:01Z

Should be fixed with e5af8e8.

MTRichards · 2013-02-14T19:05:19Z

Mac client still crashes when a large sync is paused. Sending log file from client in email.

danimo · 2013-02-14T19:07:29Z

The new build is not yet up. Only in ~5 hours..

kelleychambers · 2013-02-15T22:40:04Z

If I read "danimo" correctly, the build would be released in 5ish hours... If this is the case, where could one find the new build? It's not on the download location on the OwnCloud website. I'm having MASSIVE crashing issues... with the above mentioned "pause" and when I click "remove" to delete a sync location. This is painful.

mkormendy · 2013-02-25T04:53:46Z

This happens to me with 1.2.0 on Mac OS X Mountain Lion 10.8.2. What's the fix here?

danimo · 2013-03-22T14:50:46Z

@mkormendy use 1.2.1. I can no longer reproduce it.

mkormendy · 2013-03-22T21:04:19Z

I would use 1.2.1, but I am affected by the other bug which is more debilitating as discussed here: #272 (comment)

danimo · 2013-03-22T21:10:29Z

@mkormendy We are about to release 1.2.2, but it will drag on until early next week. The crash should be fixed there. In the meanwhile, you can try the nightly builds at http://download.owncloud.com/download/nightly/

guillermomarco · 2013-03-25T17:22:01Z

Will 1.2.2 fix csync error for large files?

danimo · 2013-03-25T18:04:09Z

@guillermomarco Please do not post in unrelated reports. It does not contain file chunking, so most likely it won't.

guillermomarco · 2013-03-26T08:49:23Z

I'm sorry. Should I open then a new issue and delete posts?

mkormendy · 2013-03-29T18:23:54Z

Just wanted ot post that release 1.2.2 seems to be working VERY well. It even growls the support. I want to get on the ownCloud creative team .. how do I contribute?

karlitschek · 2013-03-30T23:18:30Z

@mkormendy Everybody is welcome to contribute. What exactly do you want to do and what do you mean with the creative team? :-)

danimo mentioned this issue Feb 14, 2013

Mac Client 1.2.0 crash when sync paused #288

Closed

danimo closed this as completed Feb 14, 2013

MTRichards reopened this Feb 14, 2013

danimo closed this as completed Mar 22, 2013

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pausing sync causes crash #245

Pausing sync causes crash #245

Burtan commented Jan 15, 2013

woboq commented Jan 16, 2013

Burtan commented Jan 16, 2013

smessmer commented Jan 16, 2013

Burtan commented Jan 17, 2013

smessmer commented Jan 17, 2013

dragotin commented Jan 17, 2013

Burtan commented Jan 17, 2013

Burtan commented Jan 17, 2013

dragotin commented Jan 17, 2013

danimo commented Feb 6, 2013

danimo commented Feb 14, 2013

MTRichards commented Feb 14, 2013

danimo commented Feb 14, 2013

kelleychambers commented Feb 15, 2013

mkormendy commented Feb 25, 2013

danimo commented Mar 22, 2013

mkormendy commented Mar 22, 2013

danimo commented Mar 22, 2013

guillermomarco commented Mar 25, 2013

danimo commented Mar 25, 2013

guillermomarco commented Mar 26, 2013

mkormendy commented Mar 29, 2013

karlitschek commented Mar 30, 2013

Pausing sync causes crash #245

Pausing sync causes crash #245

Comments

Burtan commented Jan 15, 2013

woboq commented Jan 16, 2013

Burtan commented Jan 16, 2013

smessmer commented Jan 16, 2013

Burtan commented Jan 17, 2013

smessmer commented Jan 17, 2013

dragotin commented Jan 17, 2013

Burtan commented Jan 17, 2013

Burtan commented Jan 17, 2013

dragotin commented Jan 17, 2013

danimo commented Feb 6, 2013

danimo commented Feb 14, 2013

MTRichards commented Feb 14, 2013

danimo commented Feb 14, 2013

kelleychambers commented Feb 15, 2013

mkormendy commented Feb 25, 2013

danimo commented Mar 22, 2013

mkormendy commented Mar 22, 2013

danimo commented Mar 22, 2013

guillermomarco commented Mar 25, 2013

danimo commented Mar 25, 2013

guillermomarco commented Mar 26, 2013

mkormendy commented Mar 29, 2013

karlitschek commented Mar 30, 2013