@sakya, I think you were experiencing something completely different than us.
Updating on my problem, I think now that I've found the culprit. Things are looking good, but I'm not at 100% confidence yet until we get more production runtime.
Basically, it looks like our V8 Script Compile failures may actually be out-of-memory failures, triggered by a memory leak bug in the IIS Advanced Logging module. This is a known bug and Microsoft has released a Hot Fix: http://support.microsoft.com/kb/2925138/EN-US
We've experimented with both the work-around and the installed Hot Fix, and with those applied we've not seen the error since.
It looks as if this memory leak bug impacts the native heap, but not the managed heap, which may be why we've not experienced any other problems within our applications.
Updating on my problem, I think now that I've found the culprit. Things are looking good, but I'm not at 100% confidence yet until we get more production runtime.
Basically, it looks like our V8 Script Compile failures may actually be out-of-memory failures, triggered by a memory leak bug in the IIS Advanced Logging module. This is a known bug and Microsoft has released a Hot Fix: http://support.microsoft.com/kb/2925138/EN-US
We've experimented with both the work-around and the installed Hot Fix, and with those applied we've not seen the error since.
It looks as if this memory leak bug impacts the native heap, but not the managed heap, which may be why we've not experienced any other problems within our applications.