Brian Bergh
Brian Bergh
This is on Windows, and i've only tested it with .NET 5. This old thread is about the exact same issue with .net core vs desktop several years ago. https://github.com/dotnet/runtime/issues/15037
Hi @danmoseley , sure go ahead. 1) Yes, you are right about the relation to the link. 2) Yes, I do own the other threats, but the case is that...
When I look in the console window right when I get the issue, there is NO foreign text (nor in gray) As stated, all the code is surrounded in lock(Console.Out)...
Okay, finally I got something. This issue seems to be related to the LogTo function in EF Core. If I remove that, it all goes away. I'm not the one...
@danmoseley I think you are spot on, thank you very much for helping out with this.
Hi @danmoseley , unfortunately I can't share the code of SimpleDebugLogger as I am not the owner of it (it belongs to my company, and it contains secrets) However, I...
@ajcvickers Thats why the entire statement (color and out) is wrapped in a lock(Console.Out) { .... } - So no?
@ajcvickers Thats correct thanks, that should be fixed. But that will not cause the console to not respond to setting foreground, and nor will it set the foregroundcolor do darkgray....
@danmoseley Thanks for the tip. There is not one single console call outside the SimpleDebugLogger in the whole solution. That is the point of it, we wanted to consolidate all...
I too get a nasty exception when looping or restarting. Its random but i get it every 2 or 3 loops no matter the video source. Its a pointer exception...