Amc.txt check for completed file in DESTINATION

[phrak9]

I find my debian box with 4.8.2 often has a problem with a file and throws an exception and stopping Filebot in its tracks, I've tried increasing the JVM's memory to 512MB didn't work. Anyway... it ends up not completing the transfer or copy in this case but it logs the file name to be SKIPPED next run in AMC.txt. So unless I manually remove the AMC.txt file it will not process the file. I have always experienced some kind of errors occurring at some point or another and thats OK, and I don't see a way of exceptions and errors that can crash Filebot going away. Is there a way to make Filebot a little "smarter" and have a configuration option to check if the file has been renamed and moved or not?
Thanks!

Code: Select all

FileBot 4.8.2 (r5789)
JNA Native: 5.2.2
MediaInfo: 18.05
7-Zip-JBinding: 9.20
Chromaprint: 1.4.2
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-02-08 (r546)
Groovy: 2.5.1
JRE: Java(TM) SE Runtime Environment 10.0.2
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 4 Core / 580 MB Max Memory / 15 MB Used Memory
OS: Linux (amd64)
HW: Linux fb 3.16.0-7-amd64 #1 SMP Debian 3.16.59-1 (2018-10-03) x86_64 GNU/Linux
DATA: /root/.filebot
Package: DEB
License: FileBot License PXXXXXXXXX (Valid-Until: 2019-07-06)
Done ヾ(＠⌒ー⌒＠)ノ

Code: Select all

Feb 17 07:04:33 T transmission-daemon[35472]: Input: /srv/1TBUSB/Recents/True Lies (1994)/True.Lies.1994.720p.x264.YIFY.mkv
Feb 17 07:04:57 T transmission-daemon[35472]: Java heap space
Feb 17 07:04:57  transmission-daemon[35472]: java.lang.OutOfMemoryError: Java heap space
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.media.ReleaseInfo.getReleaseGroupTrimPattern(ReleaseInfo.java:352)
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.media.ReleaseInfo.cleanRelease(ReleaseInfo.java:168)
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.media.MediaDetection.stripReleaseInfo(MediaDetection.java:1192)
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.media.MediaDetection.detectSeriesNames(MediaDetection.java:460)
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.media.MediaDetection.detectSeriesNames(MediaDetection.java:323)
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.cli.ScriptShellBaseClass.detectSeriesName(ScriptShellBaseClass.java:261)
Feb 17 07:04:57 T transmission-daemon[35472]: at net.filebot.cli.ScriptShellBaseClass.detectSeriesName(ScriptShellBaseClass.java:249)
Feb 17 07:04:57 T transmission-daemon[35472]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Feb 17 07:04:57 T transmission-daemon[35472]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
Feb 17 07:04:57 T transmission-daemon[35472]: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
Feb 17 07:04:57 T transmission-daemon[35472]: at Script1$_run_closure50.doCall(Script1.groovy:338)
Feb 17 07:04:57 T transmission-daemon[35472]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Feb 17 07:04:57 T transmission-daemon[35472]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
Feb 17 07:04:57 T transmission-daemon[35472]: Failure (°_°)

[rednoah]

That's odd. 256 MB is already fine, and 512 MB is more than enough.

Are you sure the -Xmx512 is actually being used when deluge is calling FileBot, and not just in your bash session?

Maybe you could try the latest 4.8.5 beta builds a spin and see if that makes a difference?