Bug 301158 - Resize bug and slow down
Summary: Resize bug and slow down
Status: RESOLVED WORKSFORME
Alias: None
Product: kcachegrind
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Josef Weidendorfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-04 14:51 UTC by BRULE Herman
Modified: 2023-01-22 05:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2012-06-04 14:51:18 UTC
Hello, with my radeon HD evergreen + open source drivers, the resize on dual screen (3000x2000) is very very slow. Can you improve it. Can you drop the maximal resize size.

Thanks.

Reproducible: Always
Comment 1 Josef Weidendorfer 2012-06-04 15:17:53 UTC
By design, the map view will use any space to be able to draw more details. Thus,
the larger the view, the more drawing will be done, and the slower it gets. So
the simple solutions would be:
(1) do redrawing less often
(2) stop at a given depth to reduce drawing needs
Solution (1), ie. throtteling redraw, will make it less responsive, and triggers
bug report like your own ("resize is slow!"). Solution (2) means less detail, so
there is no reason to enlarge the window to such sizes in the first place.
So I am not sure what you are asking for.

Tips:
* part of the default redrawing is the shading effect. You can switch
it off in the context menu ("Visualization > Shading"). Does this help?
* if the radeon driver is to slow, switching to software rendering may
help: start kcachegrind with option "-graphicssystem raster".
* tell your window manager not to ask for window redrawing while
resizing is going on

> Can you drop the maximal resize size.

I did not know that there is a maximal resize size. What is the maximum
for you?
Comment 2 BRULE Herman 2012-06-04 15:38:40 UTC
1) should be the most easy.

Tips:
* That's help, but it's not quick
* Help few, but product bug too, with big resizing:
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 56 (X_ChangeGC)
  Resource id:  0x0
* kdm, I wil forward this bug repport, my maximal resize is near by 2934x771 as normal, 5000x1300 with -graphicssystem raster

At the time of Qt5, why not use QML witch help to draw this kind of graphic?
Comment 3 Josef Weidendorfer 2012-06-04 16:27:14 UTC
(1) should do your window manager, by disabling redrawings while resizing, as I said.
BTW, that is not kdm, but kwin. And this should already be a configuration option.

If the maximum resize limit depends on the rendering backend, this is a Qt bug,
and I can not do much about that (apart porting away from Qt, what I do not plan).

I do not have to for a port to QML. If you do, I will review the patch.
Comment 4 Andrew Crouthamel 2018-11-09 00:57:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-18 03:37:04 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-23 00:28:12 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2023-01-07 05:22:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-22 05:06:29 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!