This is a strange issue I have noticed several times recently in different solutions and use cases, yet cannot reliably reproduce.
Basically I never get a response to the request when the reponse includes an object to be serialized. I can see the request, and if I set a breakpoint in the controller I can follow execution through to returning the response, but the response never arrives at the browser.
In task manager I can see that IIS Worker Process runs around 32% CPU load until I force it to close.
As mentioned I have noticed this issue across several solutions with various release and pre-release versions of Entity Framework and Web API 2. It seems very strange, and if I were to take a guess it would have something to do with the serialization, but that's pure speculation (the problem goes away if I don't return the object, but e.g. just a HttpResponseMessage without content).
I'm working on Windows 8.1, VS 2013 Update 1, using EF on LocalDb. I'm happy to provide additional information, if you can direct me where to look?
Basically I never get a response to the request when the reponse includes an object to be serialized. I can see the request, and if I set a breakpoint in the controller I can follow execution through to returning the response, but the response never arrives at the browser.
In task manager I can see that IIS Worker Process runs around 32% CPU load until I force it to close.
As mentioned I have noticed this issue across several solutions with various release and pre-release versions of Entity Framework and Web API 2. It seems very strange, and if I were to take a guess it would have something to do with the serialization, but that's pure speculation (the problem goes away if I don't return the object, but e.g. just a HttpResponseMessage without content).
I'm working on Windows 8.1, VS 2013 Update 1, using EF on LocalDb. I'm happy to provide additional information, if you can direct me where to look?