Access violation in js32.dll

Hello, first of all thanks for creating this excellent tool, it is so useful and powerful I don't know what I would do without it!

I just got a new workstation (W7 65bit, Xeon E5-1650) and noticed with the new setup I am consistently getting the following error dialog when I try to add folders with more than about 400 files. Smaller folders are okay. It appears the issue is only affecting the actual display of the file grid, there is a white area now where the grid used to be and you can actually click around in the ara and see the item information changing.

---------------------------
Access violation at address 5053F7B5 in module 'js32.dll'. Read of address 03C8F03C.
---------------------------


Thanks in advance for you help resolving.

---

Reply to #1:
I should add that I have tried running in compatibility mode.

Also I forgot to mention this rather important detail. The problem only occurs when I have a script renaming method applied. Here is the script I'm using in case that might be the issue:
var str = item.exifToolValue("DateTimeOriginal");

var arrDateParts= str.split(":");
var monthNames = ["January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December"];
var month = Number(arrDateParts[1]) ;
var mn = monthNames[month-1]

var snewPath = "s:\\Photos\\Nikon D70\\"+arrDateParts[0]+"\\" + mn + "\\";
item.newPath = snewPath;

---

Reply to #1:
I'm running into this Access violation for js32.dll as well. Running AR v3.77 on Windows 10. Script is fairly simple:

if (item.exifToolValue('DateTimeOriginal') != item.exifToolValue('ModifyDate')) {
return item.newBasename + '_' + 'edited';
}
else {
return item.newBasename;
}

I was able to run this same script on a another Windows 10 laptop on a sample set of files with no problem.

---

I'm seeing the same (or a similar) problem.

It happens whenever I add large numbers of files or directories and have auto test checked and am using a rename script that calls the exiftool. I can also generate the error after I've loaded a lot of files and pressed Test Batch.

I'm pretty sure js32dll is used to wrap the calls to the exiftool. Without access to a debug build all I can do is speculate. I think we are seeing a thread collision issue where lots of threads are calling exiftool through the js32 dll and are not getting a requested resource because another thread has it locked. If I'm right, it can either be a problem in the way Advanced Renamer calls exiftool or a bug in the js32 dll. I don't know how AR is implemented, but a catch/throw block around the thread forking code that calls exiftool might mitigate the issue.

---