![lollipop ads all over firefox popups lollipop ads all over firefox popups](https://static.javatpoint.com/androidpages/images/how-to-allow-or-block-pop-ups-in-chrome-browser.png)
Even with proper double buffering, combining both frame buffers is still done on the CPU. They will redraw the entire rectangle if you try to stack things with any transparency or non-rectangle clips. By default, Qt/GTK/wx are too dumb to understand layers properly. Audacity has to redraw the entire track widget each time the needle moves unless they implement special double buffering + special damage area slices. That's probably because of the cursor animation (when you play). > which tells me this isn't a simple pixel pushing problem but rather something more profound in Audacity. Marcan_42 comment is too deep in the tree) I guess wxGTK just struggles when it has to draw 4x as many pixels? But Audacity doesn't even seem to support HiDPI mode on Linux properly to begin with (the entire UI is small), so that's not it per se. The workaround is, well, not using HiDPI mode which is silly. I kind of suspect this to be a windowing toolkit issue, and originally I thought it was macOS-specific (since I first noticed when I tried to recommend it to friends who use that), but ever since I moved to a 4K screen on Linux I noticed it's bad here too. Shrinking the window helps, but it's silly to have a tiny window and scroll around when you have a 4K display. I was just trying to listen to 10 tracks one by one yesterday and even just muting/soloing a track would take about a second it was horrible. I'm hoping this is something that improved in 3.0.0, because using Audacity is becoming increasingly impractical. It feels like it's actively gotten worse on this front. It seems to struggle badly on high-DPI displays: it is almost unusable maximized on both macOS and Linux (X11) if you have a 4K or so display. I've found the exact opposite - Audacity used to be instant, but these days its UI is dog slow.