-
Notifications
You must be signed in to change notification settings - Fork 945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iisexpress.exe crashing with TargetInvocationException #102
Comments
Interesting... Do you have any custom configuration for IIS Express or are you just using the standard config? Are you running it through Visual Studio, or outside of Visual Studio? Do you have the Visual Studio debugger attached or do you run "without debugging"? |
Standard iis express config. Running through Visual Studio (launched via On Thu, Mar 12, 2015 at 11:40 PM, Daniel Lo Nigro notifications@github.com
|
Update: I disabled pooling in ReactConfig.cs and the issue has gone away. |
I've actually been getting a very similar issue, except instead of an exception, I just get a connection refused. It happens very reliably whenever I rebuild my jsx with webpack. Re-launching via "View in Browser" gets it going again. I'm in IIS Express 8.0 if that helps. @jlchmura How did you disable the pooling? |
Yes my symptoms are the same.. if you look at your event log I'm guessing To disable pooling, add this to your ReactConfig.cs file: On Thu, Mar 19, 2015 at 12:06 PM, R notifications@github.com wrote:
|
I had this same issue. ReactSiteConfiguration.Configuration.SetReuseJavaScriptEngines(false); works wonderfully. If you are using webpack this also allows you to add the --watch flag so that your packages are rebuilt as you change your code. I'd suggest integrating that into the documentation / tutorial. If there is interest I can create a PR. |
@Daniel15 since turning off pooling solves this issue.. does that point to an issue in jspool? |
+1 on this issue. Happens to my business partner. Turning off pooling corrects the problem. Visual Studio Ultimate 2013 12.0.31101.00 Update 4 |
Some of the changes I've done to JSPool recently might fix this. @jlchmura Could you please provide the InnerException of that exception if possible? I think it'll be really useful. In the meantime you could turn off pooling only in debug builds:
|
Still seems to be happening to my partner on latest release. I'll see if I can get the exception next time he and I are together in person. |
I am getting this exception as well with latest 3 NuGet releases. Seems similar in terms of how it crashes to #28 that I submitted a while back. |
Error still occurs while debugging (probably from version 2.0). Configuration:
First exception (visible only when symbols are loaded in VS):
Second exception:
After second exception, VS turns off debugging (TargeInvocatonException kills app).
|
I've run into this ClearScript crash with IIS Express, but regular IIS (w3wp) appears to be fine. |
Using ChakraCore may work around the problem for you. |
While working with my project, the iisexpress.exe frequently crashes on me when a request is made. It may be irrelevant, but often .js files have been changed in my project since the last successful request, though they are all in folders that are not being process/packaged by react.net.
VS2013 Update 4, Windows 8.1 x64, multiple processors. Happens with React 1.4.0 and 1.3.0.
Here are the details from the event log:
The text was updated successfully, but these errors were encountered: