@Rexque My apologies, I totally forgot to check back this thread after I posted the sample program. Wasn’t until I was cleaning up a directory that I ran into the test script and realized I forgot, quite embarrassing.
I don’t recall seeing a notification email either.
Thank you for running the tests, I’m happy I created those variations seeing those different results.
Interesting is that both crash when doing the same file. But more interesting is that the 4.0 version isn’t crashing.
Can you get me the content of the 100 and 106 subdirectories as shown in the screenshot? I’d like to see if the behavior is the same for me with the same input files.
Secondly can you run https://drive.google.com/open?id=0B_knlkUin50hX3FQY2E0djdBSEk (sha1 8A824F7F665E36C7D9B04E552B6DF88AB32FD8D8)
It’s a minor variation of the first case.
@markus101 What puzzles me is that the 4.0 version is basically the test app compiled against the 4.0 framework target, just like Sonarr is. The 4.5.2 versions are obviously compiled against 4.5.2 framework, but Sonarr isn’t so why are we seeing that same error in Sonarr?
The last version (18.104.22.168/4.1.10) is the ImageResizer version and evidently doesn’t affect the outcome.
Why would the framework version affect the behavior?
The only difference is that the 4.0 compiled version is 64-bit, where the rest is preferred 32-bit and so is Sonarr.
Only after realising this I created the variation posted above which is targeting x86 specifically, like Sonarr, we’ll see if it crashes. If it does then there’s likely an issue with the 32-bit gdi or related libraries.