Activity overview
Latest activity by joebone
Hi, any progress diagnosing this issue? / comments
Hi, any progress diagnosing this issue?
@Jessica R This is a self hosted/kestrel site - I have tried both with compiling to a windows target, or having it open the dll itself. The profiling is launched from the standalone ants profiler. In both cases, it is the application itself that crashes, in kernelBase.dll, and looking at the call stack, it appears to be from t
he RcFrameConsolidation in nt.dll ( attached screenshots ).
As this is 100% reproducible, if you'd like, I can give you the binaries directly... although obviously posting on a public forum would be frowned upon [image]
Launch settings: [image]
Effect: [image]
Debugging that exception : [image]
Then when clsoing ants: [image]
Evidentally, when just running the application (via "dotnet dllname.dll") and using the appropriate environment variables, it works fine - confirmed and tested both on windows (7, 10, server 2012 and server 2016), and debian 8. So there is something in the way the profiler loads itself and dotnet.exe that causes this behaviour. Speaking of environment variables, is there any way to specify them within a profiling session for dotnet core apps? / comments
@Jessica R This is a self hosted/kestrel site - I have tried both with compiling to a windows target, or having it open the dll itself. The profiling is launched from the standalone ants profiler. ...
We also ran into the crash issue with self hosted aspnet core sites, and sent the crash reports. Any feedback would be appreciated. / comments
We also ran into the crash issue with self hosted aspnet core sites, and sent the crash reports. Any feedback would be appreciated.