Bug 89688 - Gwenview hangs after opening a picture if glamor is used
Summary: Gwenview hangs after opening a picture if glamor is used
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Acceleration/glamor (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-20 06:10 UTC by sunweb
Modified: 2015-03-27 08:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
glamor gwenview (35.95 KB, image/jpeg)
2015-03-26 07:33 UTC, sunweb
no flags Details
Xorg.0.log (43.44 KB, text/plain)
2015-03-26 16:26 UTC, sunweb
no flags Details

Description sunweb 2015-03-20 06:10:36 UTC
Kubuntu 14.04 x64, HD5770
Qt: 4.8.6
KDE Development Platform: 4.13.3
Gwenview: 4.13.1

cat /etc/X11/xorg.conf
Section "Device"
        Identifier "Device0"
        Driver  "radeon"
        Option  "AccelMethod" "glamor"
EndSection

After openin one picture Gwenview hangs and becomes unresponsive. And you can see that bottom panel is not filled with mini pictures that represent the ones in the same folder.

Reproducable only with glamor, with EXA everything works.
Comment 1 Michel Dänzer 2015-03-20 07:44:58 UTC
I can't seem to reproduce this with Gwenview/KDE 4.14.2. Can you attach screenshots showing the problem and what it looks like with EXA?
Comment 2 sunweb 2015-03-26 07:33:54 UTC
Created attachment 114639 [details]
glamor gwenview
Comment 3 sunweb 2015-03-26 07:34:24 UTC
(In reply to Michel Dänzer from comment #1)
> I can't seem to reproduce this with Gwenview/KDE 4.14.2. Can you attach
> screenshots showing the problem and what it looks like with EXA?

Ok i figured it out, its not hanging for ever. I have a folder with 7k+ pictures and with glamor it takes 2 minutes for Gwenview to load the list and become responsive again. It takes 1 second using EXA.
Comment 4 Michel Dänzer 2015-03-26 07:39:58 UTC
Please attach the /var/log/Xorg.0.log file with glamor enabled.
Comment 5 sunweb 2015-03-26 16:26:03 UTC
Created attachment 114650 [details]
Xorg.0.log
Comment 6 sunweb 2015-03-26 16:28:10 UTC
Also i've found that after those 2 minutes long of loading if you close Gwenview and then open it again everything is quite fast, it loads up in ~2 seconds.
Comment 7 Michel Dänzer 2015-03-27 01:09:05 UTC
(In reply to sunweb from comment #6)
> Also i've found that after those 2 minutes long of loading if you close
> Gwenview and then open it again everything is quite fast, it loads up in ~2
> seconds.

But with EXA, it's fast even the first time after system boot?

During those two minutes, does the Xorg process peg a CPU core? If so, can you get a profile of those two minutes with sysprof or perf?
Comment 8 sunweb 2015-03-27 06:46:15 UTC
(In reply to Michel Dänzer from comment #7)
> But with EXA, it's fast even the first time after system boot?
> 
> During those two minutes, does the Xorg process peg a CPU core? If so, can
> you get a profile of those two minutes with sysprof or perf?

I am terribly sorry. To see EXA performance i always deleted xord.conf -> logout -> login. Never tried clean system boot until you mentioned it. Glamor and EXA makes no difference. I'll report it to KDE team then.

Could sysprof help to catch the problem with this bug https://bugs.freedesktop.org/show_bug.cgi?id=89374 if i'll do 2 tests with intel and amd gpus to see the difference?
Comment 9 Michel Dänzer 2015-03-27 08:45:30 UTC
(In reply to sunweb from comment #8)
> I am terribly sorry. To see EXA performance i always deleted xord.conf ->
> logout -> login. Never tried clean system boot until you mentioned it.
> Glamor and EXA makes no difference. I'll report it to KDE team then.

Okay, thanks for the update, resolving.


> Could sysprof help to catch the problem with this bug
> https://bugs.freedesktop.org/show_bug.cgi?id=89374 if i'll do 2 tests with
> intel and amd gpus to see the difference?

Maybe not, but it might be worth a shot.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.