If I try and lookup the file "51.mp4", the GUI just stops working or processing the files. The command line gets stuck in a 100% CPU loop by looks of it.
Movie data not found: TheMovieDB::51 [51 / tt0000000] => java.io.FileNotFoundException: Resource is empty: {} => https://api.themoviedb.org/3/movie/51?language=en-US&api_key=1bb965af6888496c30d52a27e831f9c9
LookupException: Invalid Lookup: Bad ID [51]
java.util.concurrent.ExecutionException: net.filebot.web.LookupException: Invalid Lookup: Bad ID [51]
at net.filebot.ui.rename.RenamePanel$AutoCompleteAction$1.done(Unknown Source)
Caused by: net.filebot.web.LookupException: Invalid Lookup: Bad ID [51]
at net.filebot.web.MovieIdentificationService.lookupMovie(Unknown Source)
at net.filebot.ui.rename.MovieMatcher.grabMovieName(Unknown Source)
at net.filebot.ui.rename.MovieMatcher.match(Unknown Source)
at net.filebot.ui.rename.RenamePanel$AutoCompleteAction$1.doInBackground(Unknown Source)
at net.filebot.ui.rename.RenamePanel$AutoCompleteAction$1.doInBackground(Unknown Source)
It seems to think the 51 is the movie ID instead of the movie name.
$ filebot -rename *.mp4 --db TheMovieDB --action TEST -non-strict
Rename movies using [TheMovieDB]
Auto-detect movie from context [51.mp4]
Movie not found: 51.mp4
Auto-detect movie from context [Avatar.mp4]
[TEST] from [Avatar.mp4] to [Avatar (2009).mp4]
Processed 1 file
Note that 51.mp4 just can't be processed automatically, because it's too short, but that in itself can't cause an infinite loop. If you help things along by searching for 51 (2011) instead of 51 then it'll work:
$ filebot -rename *.mp4 --db TheMovieDB --action TEST -non-strict
Rename movies using [TheMovieDB]
Auto-detect movie from context [51.2011.mp4]
Auto-detect movie from context [Avatar.2009.mp4]
[TEST] from [51.2011.mp4] to [51 (2011).mp4]
[TEST] from [Avatar.2009.mp4] to [Avatar (2009).mp4]
Processed 2 files