Atom flickers really badly when switching tabs of open files (specifically a TypeScript file and a JavaScript file) with atom-typescript package installed and a tsconfig.json file in the project folder. Reproducible: Always Steps to Reproduce: 1. Install Atom text editor 2. On terminal: apm install atom-typescript (this will install Typescript package for Atom) 3. Launch Atom (it should automatically install a dependency for the package, it's a linter) 4. Open a normal folder with following files: tsconfig.json and test.ts 5. Contents of tsconfig.json can be an empty json file, with just two curly braces in it ( like {} ) 6. For test.ts, visit ' https://www.typescriptlang.org/play/ ' and copy paste the script shown on the left side of the page into test.ts. 7. After that hit CTRL + S, this will compile test.ts to test.js, in the same directory. 8. Now make sure test.ts and test.js are open in Atom editor as two tabs. 9. Now switch between tabs couple of times, if I'm not the only one, you should see white flickering in the bottom part of Atom (make sure Atom is maximised, funny enough, this does not happen at all when atom is not maximised) Actual Results: Atom flickers when fully maximised (or Atom window size is more than 60% on either axis of the screen), while switching between two tabs, of a Typescript file and a JavaScript file. With atom-typescript package installed and functional. Expected Results: Should not flicker when Atom window size is anything more than 60% on both axes of the screen. Computer: Lenovo Y50 UHD Touch screen Resolution: 3840 x 2160 @ 48hz Drivers: Nothing modified after I installed Neon out-of-box, same results with Kubuntu out-of-box and Fedora as well.
Update: All this happens ONLY when I use 3840 x 2160 with scale set to 2. When I change to 1920 x 1080 at scale 1, NO problems occur at all. But I get extremely bad experience since I've got used to a higher resolution.
Update 2: Confirmed that scaling is the culprit. Running system at 3840 x 2160 @ scale = 2, causes the issue. However scaling it down to 1 and restarting the system, completely eliminates the issue, but UI is illegible. I'm no expert in graphics or operating systems, but I think scaling adds another overhead over the compositor.
Scaling is all done in app not by the compositor. Bug is with Atom, not us.