FF 57.0 Locks up w/NoScript 10.1.2 on KEH.com

[bluloo]

Love NoScript. Been using it for years, and have donated multiple times. Keep up the great work!

Not sure if this is the correct place to notify the developer, but I'm getting browser lock-ups when browsing to KEH.com with NS enabled. with NS disabled, I can browse the site normally. KEH.com is whitelisted.
I can sometimes load their main page, but then then attempting to click through, I'll get a spinning beachball (OS X 10.13.1) and the browser freezes. I have to force quit and relaunch FF. Sometimes it locks up when loading their main page as well.

The crash is plugin-related, and repeatable. Part of the crash log pasted below, FYI (Keep getting a spam notification when attempting to post, so I cut it down). If I should submit this elsewhere, please let me know. Thanks.

Process: plugin-container [60692]
Path: /Applications/Firefox.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container
Identifier: org.mozilla.plugincontainer
Version: 1.0
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: plugin-container [60692]
User ID: 502

Date/Time: 2017-11-26 11:05:46.519 -0500
OS Version: Mac OS X 10.13.1 (17B48)
Report Version: 12
Anonymous UUID: BCDC5F40-BC6F-562D-7F1E-E14DFDE21D8C

Sleep/Wake UUID: D425E1C3-B3F0-4DD5-8C04-9A52916F8539

Time Awake Since Boot: 120000 seconds
Time Since Wake: 2700 seconds

System Integrity Protection: enabled

Crashed Thread: 3 Chrome_~dThread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0:
-->
__TEXT 00000001008a4000-00000001008a5000 [ 4K] r-x/rwx SM=COW /Applications/Firefox.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff552dbe76 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff552db390 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff2dbb45d5 __CFRunLoopServiceMachPort + 341
3 com.apple.CoreFoundation 0x00007fff2dbb3927 __CFRunLoopRun + 1783
4 com.apple.CoreFoundation 0x00007fff2dbb2fa3 CFRunLoopRunSpecific + 483
5 com.apple.HIToolbox 0x00007fff2ced2866 RunCurrentEventLoopInMode + 286
6 com.apple.HIToolbox 0x00007fff2ced25d6 ReceiveNextEventCommon + 613
7 com.apple.HIToolbox 0x00007fff2ced2354 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8 com.apple.AppKit 0x00007fff2b1cfa23 _DPSNextEvent + 2085
9 com.apple.AppKit 0x00007fff2b964e6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
10 XUL 0x0000000102a44c12 0x100b29000 + 32619538

Thread 1:
0 libsystem_kernel.dylib 0x00007fff552dbe76 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff552db390 mach_msg + 60
2 XUL 0x0000000103bbcd82 0x100b29000 + 50937218

Thread 2:
0 libsystem_kernel.dylib 0x00007fff552dbe76 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff552db390 mach_msg + 60
2 XUL 0x0000000101006708 0x100b29000 + 5101320

Thread 3 Crashed:: Chrome_~dThread
0 XUL 0x0000000101027ef7 0x100b29000 + 5238519

[Thrawn]

NoScript 10 is very much a work in progress. Does this happen with the latest version?