REQUEST FIX: Long Folder and File Names

[madsriisager]

REQUEST FIX:
I have now countless times experienced, that if the original file name of a folder and file is too long, then FileBot crashes.

This is very annoying when trying to bulk rename something and when it suddenly crashes, I have to search through my files to find the specific one, which has a too long file name.

I don't know if this is an easy fix, but maybe add a warning-pop-up which say the file name is too long, and then just skip that file and still do the rest.

[rednoah]

Thanks for the post! Before a real human comes by, please make sure your report has all the following points checked:

• What are you trying to do achieve? What's not working? What have you tried so far?
• Include screenshots, logs or filenames (i.e. demonstrate the issue)
• Include System Information (i.e. filebot -script fn:sysinfo console output)

Please read How to Request Help and Fix Problems, Report Bugs, Get Features.

[raskery]

I also appear to have this problem. I have movies in sometimes many sub-directories and when I try to rename them Filebot crashes. It appears to be a problem with Filebot not with the long filenames. If I move the file to the root directory and do the rename it works ok and then I can move the directory back to the place I originally wanted (meaning the filesystem supports the long filename).

This may have something to do with Windows 10 increasing the

maximum path length to 32,760 Unicode characters with each path component no more than 255 characters and the filename to 255 Unicode characters

in Windows 10. I think it used to be something like 255 including the path

see Maximum Path Length Limitation section in
https://docs.microsoft.com/en-us/window ... ing-a-file

and
https://docs.microsoft.com/en-us/window ... comparison

[rednoah]

Thanks for the post! Before a real human comes by, please make sure your report has all the following points checked:

• What are you trying to do achieve? What's not working? What have you tried so far?
• Include screenshots, logs or filenames (i.e. demonstrate the issue)
• Include System Information (i.e. filebot -script fn:sysinfo console output)

Please read How to Request Help and Fix Problems, Report Bugs, Get Features.

I will absolutely need System Information and file paths as text please. Additionally, if FileBot crashes, then there will be a crash log, so I'll need that too please.

[raskery]

Hi

Sorry, new to the forum.

Systeminfo below:

Code: Select all

FileBot 4.9.1 (r7372)
JNA Native: 6.1.0
MediaInfo: 19.09
7-Zip-JBinding: 9.20
Chromaprint: 1.4.3
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2020-04-20 (r634)
Groovy: 3.0.3
JRE: OpenJDK Runtime Environment 14
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 16 Core / 4.3 GB Max Memory / 655 MB Used Memory
OS: Windows 10 (amd64)
STORAGE: NTFS [(C:)] @ 4.6 GB | NTFS [(D:)] @ 390 GB | NTFS [Data1] @ 383 GB | NTFS [Data2] @ 465 GB | NTFS [Storage space] @ 305 GB | NTFS [  (H:)] @ 107 GB | NTFS [  (I:)] @ 403 GB | NTFS [TV] @ 403 GB | NTFS [Movies] @ 231 GB
DATA: C:\Users\xxxx\AppData\Roaming\FileBot
Package: MSI
License: FileBot License P11749745 (Valid-Until: 2021-02-20)

Screenshot of error:


The root filepath was

Code: Select all

K:\___Kids Movies\_Lady.and.the.Tramp

The filepath holds the directories seen in the screenshot and the rename moves the directories and files into the movies sub-directory with the same directory and file names.

It appears to start the rename creating the first directory and then exits with that error. The error.log file in %appdata%/roaming/filebot is zero bytes.

I couldn't find/enable any crashdumps.

I am using the movie format of:

Code: Select all

../Movies/{y} - {n} - [{vf}({hpi}), {vc}, {ac}, {channels}]/{y} - {n.colon(' - ')} {' CD'+pi}{subt} - [{vf}({hpi}), {vc}, {bitdepth}bit, {fps.round(0,)}fps, {ac}, {channels}]

This happens with other similar renames of other files.

Let me know if I can dig up some more information.

Cheers

[rednoah]

1.
If you click OK, does FileBot immediately shutdown?


2.
Open CMD and run filebot. This will allow you to run the GUI and see console output. Try again and see if the console says anything when it crashes.


3.
Try the FileBot (platform) launcher and see if you get the same error. This launcher disables Windows Shell integration. See if that works. It'll will help us narrow down the problem.



EDIT:


4.
The file path doesn't look super long to me, and I've never seen this particular error message. Are you sure it's a long file path problem, and not another kind of problem?

Does FileBot not prompt you to reduce the file path length?