Andrew Nosenko
Andrew Nosenko
[BUG] SkiaSharp can call WM_PAINT handler and random COM callbacks when creating or obtaning objects
No worries Brad, glad if it helped... one of those evergreen subtleties of Windows Desktop development with .NET :)
[BUG] SkiaSharp can call WM_PAINT handler and random COM callbacks when creating or obtaning objects
> Doing that on STA thread breaks .NET itself in various ways. We've initially tried to always use a non-pumping context and discovered that it breaks APIs like GC.WaitForPendingFinalizers, those...
[BUG] SkiaSharp can call WM_PAINT handler and random COM callbacks when creating or obtaning objects
> @noseratio I think using `lock` also had this issue: https://gist.github.com/retran/b57e4db1a173048c2cee49ac6d523fc2 @mattleibow I might be wrong but I think in this particular case it's caused by `Thread.CurrentThread.Join(100)`, where they call...
[BUG] SkiaSharp can call WM_PAINT handler and random COM callbacks when creating or obtaning objects
@mattleibow you were right! TIL, plain c# locks (ie., `Monitor.Enter`/`Monitor.Exit`) also pump on an STA thread 👀 https://gist.github.com/noseratio/0d93133b826339c7eaf49c9feec142e3#file-winformsapp-cs-L60 Now I wonder if there's any *managed* blocking synchronization primitive that doesn't...
Can confirm, still an issue with 1.1.3. I thought I might be doing something dumb but ended up here by while searching.
I'm also affected by this issue. It appears to be a shenanigan of both PowerShell and NPM working together. Node.js is not involved. A proof: package.json: ```json { "name": "cli-test",...
Digging more into this, the problem appears to be with `"C:\Program Files\nodejs\npm.ps1"`, which gets invoked when we type `npm` from a PowerShell prompt on Windows. OTOH, running the `npm.cmd` (`"C:\Program...
@lukekarrys, thanks for looking into this. On Windows, `--%` kind of works, but not the way `--` has worked before. On Linux, `--%` doesn't work at all, which is a...
@lukekarrys, thank you and maybe the following could help. Besides traditional `$args` (which only gives the remaining unbound args), there is a way to access the entire original command line...
@lukekarrys, I've now invested more time into this and come up with a working fix, based on what I said above. Here is a complete version of `"C:\Program Files\nodejs\npm.ps1"` file...