Crash when moving file to DropBox folder

Help & Support
1

Hi,

I'm running DO 10.0.1.0.4185.x64 on Vista x64. I'm currently often seeing DO crashing when moving a file from a regular folder to a Dropbox folder via Ctrl+X, Ctrl+V. Unfortunately, I'm unable to reliably reproduce the issue, it only happens sometimes (maybe also when moving to regular folder, but so far I've only seen it happening with Dropbox folders as the target). That's why I did not report it until now, but the issue is becoming increasingly annoying.

Is anyone else seeing this? What can I do to help debugging the issue?

Thanks.

2

Is the Dropbox software up-to-date? Someone had problems with it crashing recently and found they went away by updating the Dropbox client.

3

It's at 1.1.35, so yes, it's up-to-date.

4

Is a crash mini-dump created when it happens?

5

There's just one dump in the DOpus.Minidumps, and it's older than my last crash. But it still might have been created when the crash appeared the first time, i.e. after upgrading to DO 10 (Did I mention that I didn't see this crash with DO 9?). Where can I send the dump to? I'd prefer to not publicly attach it to this forum thread.

6

You'd normally send it to GPSoftware Support (link in my sig), but it's probably not worth it if the minidump is old and we're not sure what triggered it.

When you get the crash with Dropbox now, what kind of message is displayed?

If it's a normal Windows application crash message, run Start -> eventvwr.exe, go to Windows Logs -> Application and see if there's a recent Application Error that mentions dopus.exe and coincides with the time of the crash.

If there is, what's in the General tab (like in my screenshot showing an nvvsvc.exe crash):


7

The DO window is slightly faded out to white and a dialog box appears with two or three options whose names I forgot :smiley:

If it's a normal Windows application crash message, run Start -> eventvwr.exe, go to Windows Logs -> Application and see if there's a recent Application Error that mentions dopus.exe and coincides with the time of the crash.

Yes, there are several entries about dopus.exe, e.g. (sorry, it's German)

Fehlerhafte Anwendung dopus.exe, Version 4.0.2.1, Zeitstempel 0x4dfaccce, fehlerhaftes Modul ntdll.dll, Version 6.0.6002.18327, Zeitstempel 0x4cb74dd3, Ausnahmecode 0xc0000374, Fehleroffset 0x00000000000aca57, Prozess-ID 0x33f8, Anwendungsstartzeit 01cc3d6f3991325e.
Fehlerhafte Anwendung dopus.exe, Version 4.0.2.1, Zeitstempel 0x4dfaccce, fehlerhaftes Modul USP10.dll, Version 1.626.6002.18244, Zeitstempel 0x4bc89971, Ausnahmecode 0xc0000005, Fehleroffset 0x0000000000003e28, Prozess-ID 0x1718, Anwendungsstartzeit 01cc3aecd9d59aeb.
Fehlerhafte Anwendung dopus.exe, Version 4.0.2.1, Zeitstempel 0x4dfaccce, fehlerhaftes Modul ntdll.dll, Version 6.0.6002.18327, Zeitstempel 0x4cb74dd3, Ausnahmecode 0xc0000374, Fehleroffset 0x00000000000aca57, Prozess-ID 0x3584, Anwendungsstartzeit 01cc3a1e3926ce70.
Fehlerhafte Anwendung dopus.exe, Version 4.0.2.1, Zeitstempel 0x4dfaccce, fehlerhaftes Modul ntdll.dll, Version 6.0.6002.18327, Zeitstempel 0x4cb74dd3, Ausnahmecode 0xc0000374, Fehleroffset 0x00000000000aca57, Prozess-ID 0x1284, Anwendungsstartzeit 01cc31bfe1bf2563.
Fehlerhafte Anwendung dopus.exe, Version 4.0.2.1, Zeitstempel 0x4dfaccce, fehlerhaftes Modul ntdll.dll, Version 6.0.6002.18327, Zeitstempel 0x4cb74dd3, Ausnahmecode 0xc0000374, Fehleroffset 0x00000000000aca57, Prozess-ID 0x13dc, Anwendungsstartzeit 01cc30b14d24a433.
8

Are you doing anything involving fonts? e.g. Copying fonts to/from dropbox?

Or have you configured Opus (or Windows itself) to use a custom font?

USP10.dll in the 2nd item is to do with UniScribe, a component of Windows that draws fonts. It may be unrelated to what you're seeing, but it's possible it's a clue.

9

Nope.

I don't think so. IIRC, I've customized lister colors, but not fonts.

Maybe we can regard that as an "outlier" for now. The crash I'm getting with ntdll.dll seems to be the one that's reproducible.

10

Agreed. Unfortunately, ntdll.dll is involved in just about everything so it doesn't give us much to go on.

Does the problem only happen if you use ctrl-c/ctrl-v, or does it also happen if you use the Copy Files button on the toolbar?

It'd be interesting to know if other Dropbox users do or don't have the same problem when using ctrl-c/ctrl-v. Anyone reading who also uses it?

11

With ntdll.dll, it's always the same "Fehleroffset" / error offset. Does that narrow things down, i.e. is it some specific function entry point?

12

It is, but it's probably something generic/low-level that's called from all sorts of things. (e.g. If it's the "open a file" entry point then it won't tell us much except a file is being opened.)

A full stack trace would reveal more (e.g. the sequence of operations and DLLs leading up to the file being opened), but getting that takes a bit of work unless you've familiar with the debugging tools already. The minidump would contain that info but isn't being created for some reason. :frowning:

13

As the date of the minidump I've mentioned matches an entry in the event viewer that is like the ones above about ntdll.dll, I've sent the minidump and event viewer error message to support via email.