Avalonia: Dev Tools causes Avalonia to crash when Application targets netcoreapp2.1

Created on 1 Jun 2018  路  8Comments  路  Source: AvaloniaUI/Avalonia

To repro simply change control catalog to target netcoreapp2.1, run it press f12.

bug

Most helpful comment

This was discussed on gitter I think, the solution is to use CTRL + F12.

All 8 comments

Looks like it's a crash somewhere in unmanaged code...

Only crashes when the debugger is attached for non-native code. Otherwise stuff just fails to correctly draw on the devtools window until you force a re-render.

Maybe it's heap corruption?

Nope that's not it. Still crashes when DevTools are disabled. I think we're hitting the fact that F12 is used by Windows to trigger a native breakpoint in a focused window. Don't know why we didn't have this issue before. .NET Core 2.1 must have broken whatever was in there before to prevent this from happening. And since they don't write any windowed applications for .NET Core they wouldn't see the issue.

They have changed stuff in the debugger for sure, when I ran the debugger on AS with 2.1 I got lots of com. Errors saying interface missing, mainly unmanaged ones.

Just tested this on latest master and still hapening.

This was discussed on gitter I think, the solution is to use CTRL + F12.

Note that this doesn't seem to be a problem in netcoreapp3.0.

I'm going to add an overload of DevToolsExtensions.AttachDevTools which accepts a KeyGesture so that people using netcoreapp2.1 can change the hotkey to Ctrl+F12.

Was this page helpful?
0 / 5 - 0 ratings