-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWT native code freezee at sun.awt.windows.WGlobalCursorManager#findHeavyweightUnderCursor #878
Comments
Disabling window decoration (-Dflatlaf.useWindowDecorations=false) looks like fix issue |
Not sure how I could help 😕 The stack in your initial post shows that thread |
Hello. I'm 100% sure stuck in native code inside FlatLaf library code, but I'm don't known how found the problem |
I will try |
I think it would be better to use |
This is interesting. Thread
Here is thread
So the problem is causes by If you (temporary) change On FlatLaf side, I'll remove the invocation of |
…eze when using custom component that overrides `Component.contains(int x, int y)` and invokes `SwingUtilities.convertPoint()` (or similar) from the overridden method (issue #878)
fixed in latest |
Good day. I will test, thanks for possible fix :) |
Looks like - bug fixed, I can't reproduce for now. I had misscheck AWT-Windows thread locking. This logic also exists in IDEA (https://github.com/JetBrains/intellij-community/blob/master/platform/platform-impl/src/com/intellij/ui/BalloonImpl.java#L2011) BalloonImpl its notifications,etc component ui. |
Hello. I'm testing FlatLaf as default laf for Consulo IDE (https://github.com/consulo), which is an IDEA fork.
I want replace internal laf implementation by FlatLaf, but catch very strange freeze at sun.awt.windows.WGlobalCursorManager#findHeavyweightUnderCursor. Freeze can appear in random time (there no specific time when, app can start - I can do something, and catch UI lock, or just at start)
JRE: 21.0.2+13-b375.1 (JetBrains s.r.o.)
JVM: 21.0.2+13-b375.1 (OpenJDK 64-Bit Server VM)
Using last library version
Also tested with Adoptium JDK 21 - some issue.
Any guess?
The text was updated successfully, but these errors were encountered: