https://bugs.kde.org/show_bug.cgi?id=477820

            Bug ID: 477820
           Summary: Minimal Overlapping Window Placement freezes kwin when
                    opening very big window
    Classification: Plasma
           Product: kwin
           Version: git master
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kwin-bugs-n...@kde.org
          Reporter: fanzhuyi...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. set Window Placement to Minimal Overlapping
2. Set screen resolution to 2560x1600
3. Open konsole
4. Run `xclock -geometry 200x1600`

Step 4 can be replaced with other sizes based on your resolution. I suspect the
issue can be triggered as long as it is big enough.

OBSERVED RESULT
System freezes. Can't even switch to virtual consoles.

EXPECTED RESULT
System doesn't freeze.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0

ADDITIONAL INFORMATION

Only triggered for Minimal Overlapping, not for other window placements.

Reproduced in neon unstable.

I would argue that this bug should have high severity and priority. 
Even though the example is quite contrived, it serves to illustrate a very
general
problem of freezing when the opened window is too big. This can happen for
multiple
reasons, including apps remembering their last size. This would lead to the
entire system
being frozen upon opening a certain app (which happened to me.
These are very hard to debug, especially because there would be nothing in the
system journals.
(I had to do a alt+sysrq r before even being able to switch to a virtual
console using ctr-alt-fx !
Then I found out that kwin was using 200% cpu, and it seems to be spending most
of the time in placeSmart)

The relevant code seems to be the Placement::placeSmart function in
https://invent.kde.org/plasma/kwin/-/blob/master/src/placement.cpp?ref_type=heads

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to