Quantcast
Channel: ClearScript
Viewing all articles
Browse latest Browse all 2297

Commented Unassigned: Access Violation Exception in v8-x64.dll [115]

0
0
Hi!
We launched a new site last week that uses ClearScript to server render a React application. After launch, we get around 2-3 crashes on Access Violation Exception in w3wp.exe a day per web server. The site has around 200 concurrent users on average, with peaks up over a thousand. We use the latest version of ClearScript (5.4.7).

We see that the crash is an Access Violation Exception in v8-x64.dll and we have a few dump files from such crashes, but since we don't have any debugging symbols the stack traces doesn't give us much.

Would you be interested in looking at the crash dumps to help us figure this out? Or if you can help us with debug symbols so we can get more information out of the dumps.

Some information about how we use ClearScript:
1. We create multiple V8Runtime and V8ScriptEngine and keep them in a queue. When a request comes in, we dequeue an engine, run JS and return it back to the queue.
2. Since we don't store any JS globals we reuse the same V8 context for different visitors. But we run CollectGarbage(true) for every 30 execution. We have deployed a change this morning where we call CollectGarbage(false) instead but twice as often. Not because we think it will solve it, but see if the behavior changes.
3. We don't pass any CLR references to V8. The only thing we do is call Engine.Execute with strings of JS code. When we pass data to V8 we do that by either calling Engine.Execute or Engine.Evaluate with strings of JSON.

Any help or pointers are appreciated! We'd be happy to share code with you if you need it.
Comments: Some more info: we tried calling CollectGarbage(false) instead of CollectGarbage(true) but doing it twice as often. This seemed to make the crashes less frequent but it also made it eat memory like nothing else. This morning we deployed a new version where we dispose both engines and runtimes when we've used them 300 times. This has made a drastic improvement in memory use for us. Memory use went from 15% to 60% of 32GB RAM in a couple of hours. But since this morning it has gone from 15% to 20-25% in ten hours. Is this normal? Why do we need to dispose engines and runtimes on a regular basis instead of just running GC?

Viewing all articles
Browse latest Browse all 2297

Latest Images

Trending Articles





Latest Images