Arch Linux

Michael Gruenstaeudl

Member

Registered: 2014-12-03

Posts: 51

[SOLVED] Dropbox stalls upon program initiation - root partition full

Although I have not updated Dropbox per se in the past days, it now stalls upon program initiation. Specifically, it loads some of the underlying libraries, but then seems to hang:

michael ~ $ valgrind dropbox
...
==4673== Invalid read of size 4
==4673==    at 0x452573: PyObject_Free (in /opt/dropbox/dropbox)
==4673==    by 0x49B708: PyEval_EvalFrameEx (in /opt/dropbox/dropbox)
==4673==    by 0x4A0698: PyEval_EvalCodeEx (in /opt/dropbox/dropbox)
==4673==    by 0x49EB5E: PyEval_EvalFrameEx (in /opt/dropbox/dropbox)
==4673==    by 0x4A0698: PyEval_EvalCodeEx (in /opt/dropbox/dropbox)
==4673==    by 0x5E6987: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5B5296: PyObject_Call (in /opt/dropbox/dropbox)
==4673==    by 0x49D6CA: PyEval_EvalFrameEx (in /opt/dropbox/dropbox)
==4673==    by 0x4A0698: PyEval_EvalCodeEx (in /opt/dropbox/dropbox)
==4673==    by 0x49EB5E: PyEval_EvalFrameEx (in /opt/dropbox/dropbox)
==4673==    by 0x4A0698: PyEval_EvalCodeEx (in /opt/dropbox/dropbox)
==4673==    by 0x49EB5E: PyEval_EvalFrameEx (in /opt/dropbox/dropbox)
==4673==  Address 0x928c020 is 14,864 bytes inside a block of size 16,421 free'd
==4673==    at 0x4C2AD7F: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4673==    by 0x45CD36: _PyString_Resize (in /opt/dropbox/dropbox)
==4673==    by 0x61FBE74: ??? (in /opt/dropbox/zlib.so)
==4673==    by 0x5B9760: PyObject_CallFunction (in /opt/dropbox/dropbox)
==4673==    by 0x5A6589: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5A776A: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5A7B8E: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5B7E62: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5B999F: PyObject_CallMethod (in /opt/dropbox/dropbox)
==4673==    by 0x4B5F3E: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x4B61AE: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x4B6866: PyImport_ImportModuleLevel (in /opt/dropbox/dropbox)
==4673== 
==4673== Thread 2:
==4673== Syscall param write(buf) points to uninitialised byte(s)
==4673==    at 0x582F1CD: ??? (in /usr/lib/libc-2.22.so)
==4673==    by 0x57C66FE: _IO_file_write@@GLIBC_2.2.5 (in /usr/lib/libc-2.22.so)
==4673==    by 0x57C5D02: new_do_write (in /usr/lib/libc-2.22.so)
==4673==    by 0x57C7608: _IO_do_write@@GLIBC_2.2.5 (in /usr/lib/libc-2.22.so)
==4673==    by 0x57C6F0F: _IO_file_close_it@@GLIBC_2.2.5 (in /usr/lib/libc-2.22.so)
==4673==    by 0x57BB742: fclose@@GLIBC_2.2.5 (in /usr/lib/libc-2.22.so)
==4673==    by 0x5DABBF: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5DAC45: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5B7E62: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5B9DFF: _PyObject_CallMethod_SizeT (in /opt/dropbox/dropbox)
==4673==    by 0x5DAAA1: ??? (in /opt/dropbox/dropbox)
==4673==    by 0x5BA5CF: PyObject_CallFunctionObjArgs (in /opt/dropbox/dropbox)
==4673==  Address 0x4023010 is not stack'd, malloc'd or (recently) free'd
==4673== 

Multiple forum threads suggest to downgrade Dropbox in similar situations, and I attempted to do just that. However, neither the most recent version of Dropbox (3.8.8-1) nor a previous version (3.6.8) are able to startup successfully.

Given that I performed a general system update recently (pacman -Syu), I presume that some dependency was updated that is now incompatible with Dropbox.

Would anyone have a suggestion concerning this?

Last edited by Michael Gruenstaeudl (2015-09-01 08:35:51)

Michael Gruenstaeudl

Member

Registered: 2014-12-03

Posts: 51

Re: [SOLVED] Dropbox stalls upon program initiation - root partition full

Turned out that my root directory was full, preventing Dropbox to generate any of the temporary files it requires for program initialization. Upon clearing my pacman package directory, Dropbox started without fail.