cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Update: Find information on Dropbox support during COVID-19 here
Close

Dropbox files & folders

Get in sync with the Dropbox Community. Our users can answer all of your questions on files and folders. Join a discussion or start your own.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

My Dropbox has not been working and keeps quitting or being force quit. I have removed dropbox, it's .dropbox folder, restarted, fixed permission, and moved the folder that used to contain all my data, but I can't get dropbox to work. 

Every time after launch (maybe 10min) I notice that dropbox no longer responds and seems to download the file list forever. Using the console I found this being repeated 100s of times per second:

7/31/15 1:13:14.822 PM Dropbox[1085]: Dropbox(1085,0xb061b000) malloc: *** mach_vm_map(size=1076350976) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

 

I am not sure what causes it and I have even tried other version of dropbox (newer) but with the same result. How can I fix that? I'd like it to work like on my other macs.

 

Thanks for any suggestions that can get me back into operation.

 

-Sebastian

12 Replies 12
Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

I've have been getting this happening too. Randomly keeps quitting and have the same errors in my console log. 

Trying to sync my folders is frustrating :-( 

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

I've been getting the same problem as well. I've tried all the same things Sebastian tried; upgraded to latest version, fixed permissions, deleted the .dropbox directory. Not sure what else to try. 

The problems all started when I added a large new folder. The only thing that has synced since then is the creation of that folder in my Dropbox account. Not a single file in that folder has synced or any other changed files from this computer in Dropbox. 

My other computers connected to Dropbox continue to sync fine.

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

I've been contacting dropbox support and they advised me to try an experimental build as it appears to be crashing due to using up too much RAM 

Installing it now and will see if it manages to complete syncing before it crashes.

https://www.dropboxforum.com/hc/en-us/community/posts/204961815-Experimental-Build-3-9-36 

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

Well it crashed again over night. Looks like it isn't solved in that build.

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 2
New member | Level 2

Same here,

over 7 Day can't use Dropbox anymore on my MacBook Pro. All other Macs work fine.

I use it for business. So when the is no help oder fix, i move to copy and leave Dropbox. 

Dropbox(23157,0xa0bda1d4) malloc: *** mach_vm_map(size=9506816) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

Just to make the thread a bit longer, I also have the same issue.

 

015-09-21 16:26:47.683 Dropbox[36291:595868] PyObjCPointer created: at 0x841fcec of type ^{OpaqueJSContext=}
Dropbox(36291,0xa3107000) malloc: *** mach_vm_map(size=1617920) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
2015-09-21 16:29:56.062 Dropbox[36291:595868] 70 Dropbox 0x00001868 start + 40

It's definitely not lack of memory, May this be because I'm using OS X 10.11.0 El capitan?

EDIT: Actually, I think it is a memory leak, Dropbox went more than 3GB when importing pictures from my iPad.

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 1
New member | Level 1

Same here: after reinstalling my operating system (first Yosemite, now El Capitan) I not only have been unable to have Dropbox synchronized again, but it repeatedly crashes my computer after several hours of indexing. Looking at the console I can see many lines like this one:

6/10/15 0:54:12,748 Dropbox[431]: Dropbox(431,0xb0599000) malloc: *** mach_vm_map(size=36048076 failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

I am using Dropbox 3.10.7 now, but I have tried many versions, both stable and testing, with the same result. This is really frustrating. I suppose that this is because I have more than 600.000 files, but, still, I have been suffering this issue since three weeks ago and, specially as a paid user, I think this is simply unacceptable. 

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 2
New member | Level 2

I can confirm that I'm receiving the same error as everyone above - I did see the Dropbox process consume ~3GB memory before it crashed during photos import.  I'm on El Capitan and Dropbox 3.10.7, too.  I did try the most recent experimental build (3.11.33) with no luck.

Highlighted

Re: Despite reinstall Dropbox quite with error code 3

New member | Level 2
New member | Level 2

Start import but stuck at 0% while take 3gb of memory. And then:

14.10.15 15:57:33,750 Dropbox[75636]: Dropbox(75636,0xa336f000) malloc: *** mach_vm_map(size=4194304) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

 

14.10.15 15:57:33,750 Dropbox[75636]: <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'bytes'

 

14.10.15 15:57:33,752 Dropbox[75636]: (
0 CoreFoundation 0x921d19b9 __raiseError + 201
1 libobjc.A.dylib 0x96a46f11 objc_exception_throw + 276
2 CoreFoundation 0x92161bc1 -[NSException raise] + 17
3 _objc.so 0x09551d09 PyObjCErr_ToObjCWithGILState + 57
4 _objc.so 0x09538ff0 PyObjCFFI_MakeClosure + 5472
5 libffi.6.dylib 0x0811db48 ffi_closure_SYSV_inner + 168
6 libffi.6.dylib 0x0811e3e2 ffi_closure_SYSV + 34
7 ImageCaptureCore 0x9a496f2e -[ICCameraDevice handleCommandCompletion + 3190
8 libobjc.A.dylib 0x96a409e4 -[NSObject performSelector:withObject + 70
9 ImageCaptureCore 0x9a485bc7 -[ICCommandCenter handleCompletionEvent:replyEvent + 460
10 ImageCaptureCore 0x9a486c82 -[ICCommandCenter handleMachMessage + 431
11 Foundation 0x90231412 __NSFireMachPort + 417
12 CoreFoundation 0x920d45aa __CFMachPortPerform + 330
13 CoreFoundation 0x920d4455 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 53
14 CoreFoundation 0x920d43c0 __CFRunLoopDoSource1 + 512
15 CoreFoundation 0x920cb909 __CFRunLoopRun + 2649
16 CoreFoundation 0x920cac46 CFRunLoopRunSpecific + 390
17 CoreFoundation 0x920caaab CFRunLoopRunInMode + 123
18 HIToolbox 0x9651a719 RunCurrentEventLoopInMode + 267
19 HIToolbox 0x9651a51b ReceiveNextEventCommon + 503
20 HIToolbox 0x9651a314 _BlockUntilNextEventMatchingListInModeWithFilter + 99
21 AppKit 0x97c4a976 _DPSNextEvent + 1053
22 AppKit 0x97c49ef0 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue + 1057
23 AppKit 0x97c49ac7 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue + 121
24 AppKit 0x97c3d23b -[NSApplication run] + 1063
25 libffi.6.dylib 0x0811e2fd ffi_call_SYSV + 29
26 libffi.6.dylib 0x0811d893 ffi_call + 275
27 _objc.so 0x0953d615 PyObjCFFI_Caller + 2501
28 _objc.so 0x09560bca PyObjCSelector_GetMetadata + 1578
29 Python 0x05a77393 PyObject_Call + 99
30 Python 0x05b13c42 PyEval_EvalFrameEx + 10274
31 Python 0x05b110fd PyEval_EvalCodeEx + 1357
32 Python 0x05b17b84 _PyEval_SliceIndex + 820
33 Python 0x05b14369 PyEval_EvalFrameEx + 12105
34 Python 0x05b110fd PyEval_EvalCodeEx + 1357
35 Python 0x05b17b84 _PyEval_SliceIndex + 820
36 Python 0x05b14369 PyEval_EvalFrameEx + 12105
37 Python 0x05b110fd PyEval_EvalCodeEx + 1357
38 Python 0x05b17b84 _PyEval_SliceIndex + 820
39 Python 0x05b14369 PyEval_EvalFrameEx + 12105
40 Python 0x05b110fd PyEval_EvalCodeEx + 1357
41 Python 0x05b17b84 _PyEval_SliceIndex + 820
42 Python 0x05b14369 PyEval_EvalFrameEx + 12105
43 Python 0x05b17c30 _PyEval_SliceIndex + 992
44 Python 0x05b14369 PyEval_EvalFrameEx + 12105
45 Python 0x05b110fd PyEval_EvalCodeEx + 1357
46 Python 0x05b10ba7 PyEval_EvalCode + 87
47 Python 0x05b37413 PyRun_SimpleFileExFlags + 755
48 Python 0x05b38e18 PyRun_SimpleFile + 40
49 Dropbox 0x00004264 main + 10084
50 Dropbox 0x00002093 main + 1427
51 Dropbox 0x0000193d start + 253
52 Dropbox 0x00001868 start + 40
53 ??? 0x00000001 0x0 + 1
)

 

14.10.15 15:57:34,042 garcon[75686]: Disconnected from Dropbox.

14.10.15 15:57:34,042 garcon[75685]: Disconnected from Dropbox.

14.10.15 15:57:34,275 com.apple.xpc.launchd[1]: (com.getdropbox.dropbox.62432[75636]) Service exited due to signal: Killed: 9

Polls
Do you know how to organize your files and folders?
We have created a guide on folder best practice, so you can get organized now check it out here.

Work Smarter with Dropbox

The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.

Sound good? Let's get started.
Who's talking

Top contributors to this post

What do Dropbox user levels mean?
Need more support?