https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #77 from Alexander Schlarb <alexander-kde@ninetailed.ninja> --- Please just keep in mind that the current first-use experience is absolutely abysimal for everybody using the described configuration: You log into an up-to-date system with plasmashell and everything will appear to work fine. A few minutes/hours (depending on configuration) your system will inexplicietly become slow and finally either your KDE desktop or (more likely) your entire system will crash/hang. This will happen every time you use KDE, but not on whatever DE/OS you came from and there won't be any obvious reason. Likely you won't be using KDE for a long time after having such an experience a couple of times. (The people here bothering to dig up such a hard to grasp issue are the absolute minority, please don't forget that.) Yes, I'm very much advocating that `QSG_RENDER_LOOP=threaded` be made default at least on Desktop MESA platforms. > Presumably the VRAM memory leak in the basic render loop should be found and > fixed. Is Qt actively working on that? Or will they just stand by on this issue “'cause the threaded one is better anyways”? I guess what I'm asking is this (and absolutely correct me if I got a wrong impression of the situation!): Is there anything important that Qt needs QSG_RENDER_LOOP=basic for, that QSG_RENDER_LOOP=threaded cannot do? Because presumably the basic loop was originally written first and then threaded got added for getting some extra performance at the cost of complexity, so it was decided to only enable it on (GL) platforms known to be “good”. So, assuming that my assumption on how this developed is correct, I'm asking you if there is any reason for them (or anybody) to keep the basic render loop in good shape, when the threaded one gets the job done anyway on all platforms they consider important and their long run goal is phase out usage of the basic loop anyways? -- You are receiving this mail because: You are watching all bug changes.
