Severe performance penalty found in VSCode rendering loop
https://github.com/microsoft/vscode/issues/272155
#HackerNews #VSCode #Performance #Rendering #Issue #Microsoft #GitHub #TechNews #Coding
Remember my #issue with same hard- and software but one device doesn't support the native resolution of an external TFT?
I could fix it today with the help of #Claude #AI using its #Opus 4.1 #LLM: https://karl-voit.at/2025/09/14/fix-wrong-34-TFT-resolution/
As so often, it was actually a layer-8-issue. I unintentionally got a Debian testing kernel on the host that worked with the TFT. After using the testing kernel on the other host, the TFT now works on both machines.
However, I now need to find out how to *not* get testing packages for my systems where I don't want it ... different issue.
@alienghic @gnomon thanks for your help! 🙇
Would you help me with an issue? Two almost identical #Lenovo #x13 2-in-1 Gen 5: one is able to use the correct screen resolution of an external TFT, the other one not.
Here's what I did so far: https://karl-voit.at/2025/09/14/fix-wrong-34-TFT-resolution/
The only thing with a difference I found so far is within the output of "lspci -v" which lists different capabilities. But I don't know what to do next ...
Remember my #issue with same hard- and software but one device doesn't support the native resolution of an external TFT?
I found some time to re-test certain things:
Issue sticks to the SSD when switched between the 2 #X13 devices -> it's a software bug.
Same BIOS settings, same GRUB settings, same BIOS firmware but different "Capabilities" reported by "lspci -v":
https://karl-voit.at/2025/09/14/fix-wrong-34-TFT-resolution/
Got any further idea I can check?