https://bugs.kde.org/show_bug.cgi?id=372305
--- Comment #58 from Jiri Palecek <jpale...@web.de> --- (In reply to Vlad Zahorodnii from comment #57) > Git commit ddd60a0c1b6a6bbf7a1ba7e34cdc63582048b862 by Vlad Zahorodnii, on > behalf of Aleix Pol. > Committed on 11/01/2023 at 14:37. > Pushed by vladz into branch 'master'. > > backgroundcontrast: Guard against calling a nullptr > > There are cases where GLVertexBuffer::map will return null (as seen in > kwinglutils.cpp:1816) which does happen (as seen in the backtrace of bug > 462017) > Make sure we don't call the null map in that case. > https://invent.kde.org/plasma/kwin/commit/ddd60a0c1b6a6bbf7a1ba7e34cdc63582048b862 Are you sure this fixes the problem? In many of the backtraces, you can see that the map pointer isn't actually zero, although some of the backtraces seem different and I suspect they might indicate a different problem. Did you try to reproduce it and confirm it is fixed, by the procedure in my other comment? I used to have this problem, but since then I've changed my computer. I still have the graphics card in question around so maybe I could try to see what it does, but I can't promise anything. Without a clear idea of what's wrong and how to fix it, I don't think this can move forward. It seems like some peculiarity of NVidia drivers, but then again, other gl apps don't crash on Nvidia, or do they? -- You are receiving this mail because: You are watching all bug changes.
