{"action":"created","issue":{"url":"https://api.github.com/repos/reactjs/React.NET/issues/28","repository_url":"https://api.github.com/repos/reactjs/React.NET","labels_url":"https://api.github.com/repos/reactjs/React.NET/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/reactjs/React.NET/issues/28/comments","events_url":"https://api.github.com/repos/reactjs/React.NET/issues/28/events","html_url":"https://github.com/reactjs/React.NET/issues/28","id":36438447,"number":28,"title":"Access Violation Exception when running JSX handler in Visual Studio debugging session","user":{"login":"paulirwin","id":1874103,"avatar_url":"https://avatars.githubusercontent.com/u/1874103?v=3","gravatar_id":"","url":"https://api.github.com/users/paulirwin","html_url":"https://github.com/paulirwin","followers_url":"https://api.github.com/users/paulirwin/followers","following_url":"https://api.github.com/users/paulirwin/following{/other_user}","gists_url":"https://api.github.com/users/paulirwin/gists{/gist_id}","starred_url":"https://api.github.com/users/paulirwin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulirwin/subscriptions","organizations_url":"https://api.github.com/users/paulirwin/orgs","repos_url":"https://api.github.com/users/paulirwin/repos","events_url":"https://api.github.com/users/paulirwin/events{/privacy}","received_events_url":"https://api.github.com/users/paulirwin/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/reactjs/React.NET/labels/Bug","name":"Bug","color":"fc2929"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":25,"created_at":"2014-06-25T00:18:59Z","updated_at":"2016-06-08T13:47:31Z","closed_at":"2014-08-23T06:21:23Z","body":"Please note that this is not a consistently reproducible issue AFAICT.\r\n\r\nOccasionally, and this seems to be about on average once an hour or so during active development, when going through this process (my normal react.js dev workflow) it results in a catastrophic Access Violation Exception:\r\n\r\n1. Start the Visual Studio 2013 debugger for my ASP.NET MVC project that uses React.NET.\r\n2. Make some changes to my JSX file in Sublime. Hit Save.\r\n3. Go over to Chrome, hit refresh. This requests the JSX file from the React.NET JSX handler again.\r\n4. If successful, the JSX handler will return the compiled JS, then I'll test it and probably go back to step 2 again, keeping the same debugger session active. But occasionally here I'll get Visual Studio popping up saying that the \"Unknown Handler\" had an Access Violation Exception. After clicking OK, the process crashes, and Visual Studio stops debugging.\r\n5. After a crash like this, without modifying the JSX file, I'll re-start the debugging session in VS, call the .jsx URL again executing the handler, and it will compile the JS just fine (meaning there's nothing wrong with the JSX itself).\r\n\r\nDue to the obscure nature of the exception, that it says \"Unknown Handler\", and that I have no call stack or target site, I can't give any further information about the exception itself. I assume it is occurring in the MSIE integration layer, but that is just a guess. I also have yet to deploy this app to any kind of production environment, so this is at least a developer environment / IIS Express issue. I can not confirm if this does or does not happen using full IIS.\r\n\r\nWhile I can't do anything explicitly to reproduce this, I can say that this happens at least under this criteria:\r\n* Keeping the Visual Studio debugging session active across multiple JSX file changes \r\n* This exception has not yet occurred on the first load -- it has always been after I've saved the JSX file a couple times and reloaded the page/called the JSX handler again a few times.\r\n* If it matters, I am not editing the file in Visual Studio (using Sublime 3)\r\n\r\nAnd, if it's relevant (due to the MSIE engine), here's my system info:\r\n* Windows 8.1 update\r\n* IE 11.0.9600.17126\r\n\r\nIf you would like me to try anything explicitly on my machine to try to reproduce this issue, let me know and I'd be happy to help. Also, I'm interested to know if anyone else has encountered this issue."},"comment":{"url":"https://api.github.com/repos/reactjs/React.NET/issues/comments/224593813","html_url":"https://github.com/reactjs/React.NET/issues/28#issuecomment-224593813","issue_url":"https://api.github.com/repos/reactjs/React.NET/issues/28","id":224593813,"user":{"login":"beruic","id":724716,"avatar_url":"https://avatars.githubusercontent.com/u/724716?v=3","gravatar_id":"","url":"https://api.github.com/users/beruic","html_url":"https://github.com/beruic","followers_url":"https://api.github.com/users/beruic/followers","following_url":"https://api.github.com/users/beruic/following{/other_user}","gists_url":"https://api.github.com/users/beruic/gists{/gist_id}","starred_url":"https://api.github.com/users/beruic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/beruic/subscriptions","organizations_url":"https://api.github.com/users/beruic/orgs","repos_url":"https://api.github.com/users/beruic/repos","events_url":"https://api.github.com/users/beruic/events{/privacy}","received_events_url":"https://api.github.com/users/beruic/received_events","type":"User","site_admin":false},"created_at":"2016-06-08T13:47:31Z","updated_at":"2016-06-08T13:47:31Z","body":"I get this consistently in VisualStudio 2015 using both IIS Express and running the program + running it from console.\r\n\r\nI use  the sample project from https://github.com/reactjs/React.NET/tree/master/src/React.Sample.Mvc6. Only change I made is in `project.json` where I put\r\n\r\n    \"React.Core\": \"2.4.0\",\r\n    \"React.AspNet\": \"2.4.0\"\r\n\r\ninstead of the existing dependencies."}}
{"actor":{"display_login":"beruic"}}