Forum Discussion
Dev channel update to 81.0.403.1 is live
Hello Insiders, today we’re releasing build 81.0.403.1 to the Dev Channel. One thing that we didn’t get a chance to mention last week was that we had to temporarily disable casting. It’s still func...
I'm seeing some intermittent text/font corruption on this Dev build on 3 different machines. (2 Intel 1 Nvidia) josh_bodner
I'm also noticing intermittent text corruption in the 81.0.403.1 build on my system with Intel UHD 620 integrated graphics.
- Looks like a universal problem of this week's Edge dev release
https://techcommunity.microsoft.com/t5/discussions/some-text-displayed-as-gibberish/m-p/1144541
Just to also confirm. Also getting some sort of Chrome render machine bug distorting fonts. Chrome itself has had to deal with this in some past versions, if memory serves. Random. Cleared temporarily by selecting or scrolling. Looks like this:
jbart007, josh_bodner and Heath Bates
I'm also encountering text rendering issues like you'd described occurring when selecting text after updating to Edge v81.0.403.1 and also installing KB4528760 and KB4532938 for Win10, like seen in the below screenshot:
I've provided some additional details (as well as referenced your comments) in my attempts to narrow down under what circumstances this occurs in a new thread:
Bug: Selecting Text Causing Other Lines to Render as Random Characters (in Edge v81.0.403.1)Hopefully, that new thread will at least help save time for others encountering the issue and considering submitting bug reports regarding it or provide some more details to help narrow down and fix the issue.
The issue remains in some cases even after deselecting text, and appears intermittent, as I'd detailed in that thread. Alt-tabbing and other cases where rendering/repaint gets triggered again result in different random characters appearing each time.
Please feel free to chime in, in that thread, if have any further details to add.
- 1. the problem is only happening in Edge Dev channel, other channels like stable or Canary don't have that problem.
2. Windows 10 updates don't have effects on it, very unlikely, because I'm on insider fast ring, didn't install those updates that belong to stable Windows 10, yet I could easily reproduce that bug on Edge Dev.
3. best thing is to wait it out, the fix is already included in Canary, so on the next major update, Dev will also receive the bug fixes.
jbart007 yes, that's what it looks like. For some reason the picture I'm trying to upload just won't go.
Heath Bates it looks like this, right?
We're aware of it and investigating. Right now, we suspect it's something we inherited from Chromium.
