Libzmq.dll crashes Directory Opus

[meridian]

I originally reported this to D Opus support, who replied as follows:

All the crashes you submitted were in a third-party DLL called libzmq.dll loaded into the Opus address space.

It’s not part of Opus - it seems to be part of something called NetDrive3 (full path to the DLL is C:\Program Files (x86)\Bdrive\NetDrive3\x64\libzmq.dll).

Unfortunately there’s not much more we can tell at this end, but if you send the same dump files to their tech support they should be able to find out where in their code the crash is occurring.

Can you help, please?

David

[tsjeong]

Hello meridian,

Thank you for the report, and thanks to the Directory Opus team for the pointer — their analysis is correct, and we can explain what our DLL is doing there.

Why libzmq.dll is inside Directory Opus

NetDrive installs a Windows shell extension (NetDriveShell_NetDrive3.dll) that draws the overlay icons on NetDrive drives — connection status and file-lock badges. Like Explorer, third-party file managers such as Directory Opus load shell extensions into their own process, and our extension brings along libzmq.dll, the library it uses to talk to the NetDrive background service. So its presence in the Opus address space is expected — but a crash inside it is our bug to fix, and we’d like to get to the bottom of it.

Could you send us three things?

1. The crash dump files — the same ones you sent to the Opus team.
2. Your NetDrive version (shown in the About screen).
3. When the crashes happen — while browsing a NetDrive drive in Opus, at Opus startup, when closing Opus, or seemingly at random? This narrows the suspect code path considerably.

If possible, please also attach the NetDrive debug logs: first set the NetDrive Log Level to VERBOSE, reproduce the problem, and then attach the log files by following the instructions below:

How to attach a log file

1. Change Log Level First, check your settings and change log level to VERBOSE. 1A. If you cannot login At your login screen: [image] Click SETTINGS at the lower right corner. Change Log level to VERBOSE and go back to login screen to apply the change: [image] 1B. If you can login Go to Settings: [image] Change log level to VERBOSE: [22] Set to DEBUG if you use old version because there is no VERBOSE log level. Go back to DRIVES screen. Changed log level takes effect when you leave …

In the meantime — a workaround that stops the crashes

You can unload our shell extension without affecting NetDrive itself. In a Command Prompt run as administrator:

regsvr32 /u “C:\Program Files (x86)\Bdrive\NetDrive3\x64\NetDriveShell_NetDrive3.dll”

then restart Directory Opus (and Explorer, or reboot). Your NetDrive drives will keep working normally; you only lose the overlay icons (status/lock badges) in file managers. To turn the extension back on later, run the same command without /u. Reinstalling or updating NetDrive also re-registers it.

Once we have the dumps we will trace the exact crash location in our code and follow up here.

Thank you.