reactjs.net - 'potential stack overflow detected' error

Question

Since I've decided to switch to server-side rendering from client-side react, I began to create my components and use them in the app.

However I came across this error:

Unknown error (RangeError); potential stack overflow detected

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: Microsoft.ClearScript.ScriptEngineException: Unknown error (RangeError); potential stack overflow detected

And this is a part from the stack-trace

[ScriptEngineException: Unknown error (RangeError); potential stack overflow detected]
   V8Exception.ThrowScriptEngineException(V8Exception* ) +169
   Microsoft.ClearScript.V8.V8ContextProxyImpl.Execute(String gcDocumentName, String gcCode, Boolean evaluate, Boolean discard) +462
   Microsoft.ClearScript.V8.<>c__DisplayClass1b.<Execute>b__19() +197
   Microsoft.ClearScript.ScriptEngine.ScriptInvoke(Func`1 func) +70
   Microsoft.ClearScript.V8.V8ScriptEngine.BaseScriptInvoke(Func`1 func) +49
   Microsoft.ClearScript.V8.<>c__DisplayClass25`1.<ScriptInvoke>b__24() +45
   Microsoft.ClearScript.V8.?A0x792c8756.LockCallback(Void* pvArg) +9
   Microsoft.ClearScript.V8.V8ContextProxyImpl.InvokeWithLock(Action gcAction) +176
   Microsoft.ClearScript.V8.V8ScriptEngine.ScriptInvoke(Func`1 func) +118
   Microsoft.ClearScript.V8.V8ScriptEngine.Execute(String documentName, String code, Boolean evaluate, Boolean discard) +118
   JavaScriptEngineSwitcher.V8.V8JsEngine.InnerEvaluate(String expression) +89

So I don't know what causes this error but I think it is some code that goes in a loop or something similar. Furthermore if I refresh the page this error goes away and if I continue to refresh intensively it shows up again which is very frustrating.

well, if you have a potential stack overflow, you came to the right place — kinakuta
– kinakuta, Commented Jul 28, 2016 at 14:12

dgpedro · Accepted Answer · 2016-11-08 14:50:47Z

I was getting the same error (web app in azure) and after some investigation and tests, setting SetAllowMsieEngine to true did in fact fixed the issue also to me.

As Luke McGregor said, this seems to be an issue with V8ScriptEngine and using SetAllowMsieEngine does the job, however this method is latest version of react.net is deprecated and is recommended to "managed in the JavaScriptEngineSwitcher configuration".

So the solution I found so far is to switch js engine switcher by setting it directly in code:

JsEngineSwitcher engineSwitcher = JsEngineSwitcher.Instance;
engineSwitcher.EngineFactories
    .AddChakraCore()
    .AddMsie( new MsieSettings() { EngineMode = JsEngineMode.Auto } );

engineSwitcher.DefaultEngineName = ChakraCoreJsEngine.EngineName;

Like this I'm using ChakraCore engine rather than default V8 which was causing the error.

So far, during our performance tests with around 250 concurrent requests, we do not have this error anymore when previously in the same conditions for sure this error would have occurred.

undefined · Accepted Answer · 2016-07-29 00:49:23Z

1

This is a known issue, see https://github.com/reactjs/React.NET/issues/190

The work around is to not use V8 to do the render ie:

app.UseReact(config =>
        {
            config
                // ..other configuration settings
                .SetAllowMsieEngine(true);
        });

answered Jul 29, 2016 at 0:49

undefined

34.4k23 gold badges135 silver badges203 bronze badges

8 Comments

Martin Shishkov Over a year ago

yes, I saw this github issue when I searched for this error and apparently it was the only relevant post on the subject so far. Anyway where should I insert the code you provided? I suspect it has to be in the Startup.cs file but my app doesn't have a UseReact() method...

undefined Over a year ago

@MartinShishkov By default it sits in App_Start\ReactConfig.cs (on ReactSiteConfiguration.Configuration) but startup is the nicer place

Martin Shishkov Over a year ago

Do you mean I should do ReactSiteConfiguration.Configuration.SetAllowMsieEngine(true); in the Configure() method in ReactConfig.cs?

undefined Over a year ago

Yup, I think that should stop the exception, the comment on the method has changed slightly since last i looked. But the idea is not to use V8

Martin Shishkov Over a year ago

Okay, I have set the configuration and we'll see where this leads. Furthermore on the github issue that you suggested there was this link - https://clearscript.codeplex.com/discussions/650824 and they say that this line of code (typeof _myVariable !== 'undefined') might cause some problems. I have the same statement in my code so do you think I should replace it with something similar?

|

Collectives™ on Stack Overflow

reactjs.net - 'potential stack overflow detected' error

2 Answers 2

Comments

8 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

8 Comments

Your Answer

Sign up or log in

Post as a guest

Related