Crash on one folder with more than 260 characters

[Saul Herrera]

Purchased OneCommander because it could handle 260+ characters.

It was working fine for a few weeks but now it crashes on the same folder.

I see the triangle exclamation point warning about the 260-character limit then I open it and it crashes.

Funny thing is...I can open it in Windows Explorer! very weird.

I looked for special characters in the filenames and found none.

Version 3.51.2.0 PRO License

Any ideas?

[OneCommander Support]

Are you saying that the same folder could be opened several weeks ago but now it crashes?

Try collapsing the preview pane before opening the folder.

Does it list content before crashing?

Window just disappears or it shows some error message? OC icon in System Tray and View log might show if there was an error logged.

I am not sure what could have changed. Do you know which version was working? (If you remember when you updated you can see in the logs folder one with that date with text Updated from xx to xx (About>Settings location; then \Logs)

These are previous versions and maybe you can try 3.48 extracting in some new folder, close current one (since two can't run at the same time) and try opening that folder

onecommander.com/OneCommander3.48.2.3.zip

onecommander.com/OneCommander3.49.0.0.zip

onecommander.com/OneCommander3.50.1.0.zip

onecommander.com/OneCommander3.50.1.0.zip

I made a quick version that might show an error

onecommander.com/OneCommander3.52.0.1.zip

Copy full path (not folder itself) of that folder where it crashes (from Explorer's address bar)

Then in OC hold Alt while clicking About button, and if there is an error that can be caught, a message box will show

Thanks!

[Saul Herrera]

Faulting application name: OneCommander.exe, version: 3.51.2.0, time stamp: 0x64fb88c1

Faulting module name: PDFShell64.dll, version: 23.3.20284.0, time stamp: 0x64e0227f

Exception code: 0xc0000409

Fault offset: 0x000000000001fa54

Faulting process id: 0x4e30

Faulting application start time: 0x01d9e6914f83cc25

Faulting application path: C:\Program Files\OneCommander\OneCommander.exe

Faulting module path: C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\PDFShell64.dll

Report Id: c39ed1b1-c9b2-4572-b5bd-1b476cedbc70

Faulting package full name: 

Faulting package-relative application ID:

[OneCommander Support]

It looks like Acrobat's thumbnail handler: PDFShell64.dll crashes when getting thumbnail and takes OC down with it.

It also looks like you have Settings>Preview>

[ ] Custom Pdf and Ai thumbnail extraction 

as unchecked (so it uses system one, in which case it uses that PDFShell64.dll that doesn't handle long paths)

To fix:

Enable the above option (uses OC's pdf extraction instead of system)

You can also enable Use local thumbnails on the same settings page so it can cache those pdf thumbnails and doesn't need to extract each time

[Saul Herrera]

Thanks, that makes sense.

 I will change those settings so that it doesn't happen again.

We ended up "fixing" it by setting the folder to "online only" (it is a Dropbox Folder) then we waited for it to sync. Then we set it to "Make available offline" and waited for it to sync again. Then we were able to enter the crashing folder without a problem.

However, I will change the recommended settings above so that it, hopefully, helps prevent the issue from returning in the future.

Thank you.

[OneCommander Support]

I did another test and opened Explorer to a folder with 1000 characters in path that has a pdf in it. When I switched Explorer to thumbnail grid mode the Explorer crashed. It is definitely caused by Acrobat's option to enable Thumbnail handler. OC was fine with it using the built-in thumbnail extractor.