https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #5 from Martin Senftleben <li...@drmartinus.de> --- (In reply to cwo from comment #3) > I'm not suggesting you switch to Wayland permanently, just to test if it > also happens there, so we can narrow down the circumstances when this > happens. I know that there are still features missing from Wayland that some > people rely on, and that it doesn't work satisfactorily for others. Sure, but I don't know how long it takes until it happens, it's not predictable. E.g. today there was no such incidence yet. On other days it is every half an hour or so. Maybe I'm doing something that triggers it, but I haven't found that out yet. I'll keep an eye on it. > If you place a smaller window away from the top border of the screen, does > it also move up? And are you using display scaling, or is it set to 100%? Yes, smaller windows not at the top border also get moved up, but not all, only a few, in total two or three. I don't know what you mean by display scaling, I guess I don't use that since I don't know it. Where can I check what it is set to? > Regarding the freezing, one thing that can cause such freezes is running out > of ram. The computer will work for a while until it decides that enough is > enough and stops a process to free up some memory. Is there a chance that > this might be happening? No, definitely not. I have a RAM monitor active all the time, it shows usually 30% to 70% used up. But besides that: it is always connected to the moving of windows, so why should it do that before it freezes? And when it freezes, I can move the mouse freely, which is usually not possible when RAM is full (I have that experienced often enough). And the time span until it works again is all more or less the same, no processes have been killed (which would be the case if RAM is full - then always the most demanding apps get shut down usually in order to free up RAM). -- You are receiving this mail because: You are watching all bug changes.
