From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99236] System (seems to) completely freezes when interacting with java swing applications.
Date: Sat, 31 Dec 2016 13:46:37 +0000 [thread overview]
Message-ID: <bug-99236-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1992 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99236
Bug ID: 99236
Summary: System (seems to) completely freezes when interacting
with java swing applications.
Product: DRI
Version: DRI git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: tmp6154@yandex.ru
I'm not completely certain whether it's related to AMD GPU driver or not, but
it's rather strange issue that I can get stable reproduce for.
I'm running a Gentoo system with AMD Radeon RX 480, with git AMD GPU driver and
git version of mesa. When interacting with scrollable JTextAreas in Java Swing
application, I get a stably reproducible issue (100%). Since this affects
multiple java swing applications (e.g. eclipse), including the program I'm
developing at the time, I can attempt to put together a reproducer java app, if
that's needed.
For first 2-3 seconds, mouse cursor moves jittery, then it stops to move at all
and display keeps displaying same frozen state. Nothing appears to work,
including Ctrl+Alt+F1, etc. But despite machine looking completely locked up,
in fact, it's not. I can ssh into it and issue reboot command. During that
time, display doesn't shows any signs of life until the moment when machine
reboots (but I can hear KDE shutdown sound).
This occurs only under JRE8, both icedtea and oracle variants. Under JRE7 issue
doesn't trigger. If memory serves, JRE8 brought improvements to
hardware-accelerated GUI rendering. This is especially strange, since Swing GUI
framework renders it's own GUI widgets.
Considering that even Ctrl+Alt+F1 doesn't work, I suppose problem happens on
kernel level, possibly in AMD GPU driver.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3302 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-12-31 13:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 13:46 bugzilla-daemon [this message]
2016-12-31 13:47 ` [Bug 99236] System (seems to) completely freeze when interacting with java swing applications bugzilla-daemon
2016-12-31 13:50 ` bugzilla-daemon
2017-01-02 16:13 ` bugzilla-daemon
2017-01-03 8:54 ` bugzilla-daemon
2017-01-03 9:00 ` bugzilla-daemon
2017-01-03 9:43 ` bugzilla-daemon
2017-01-07 8:00 ` bugzilla-daemon
2017-01-07 11:28 ` bugzilla-daemon
2017-01-07 11:53 ` bugzilla-daemon
2017-01-07 12:16 ` bugzilla-daemon
2017-01-09 7:18 ` bugzilla-daemon
2017-01-09 19:12 ` bugzilla-daemon
2017-01-09 19:35 ` bugzilla-daemon
2017-01-10 17:22 ` bugzilla-daemon
2017-01-10 18:45 ` bugzilla-daemon
2017-01-10 19:23 ` bugzilla-daemon
2017-01-11 9:43 ` bugzilla-daemon
2017-01-12 16:56 ` bugzilla-daemon
2018-04-04 10:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99236-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.