Skip to content
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

[Composer] drawing rectangle causes high CPU usage resulting in hang ups #18287

Closed
qgib opened this issue Mar 6, 2014 · 5 comments
Closed

[Composer] drawing rectangle causes high CPU usage resulting in hang ups #18287

qgib opened this issue Mar 6, 2014 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Mar 6, 2014

Author Name: Evaldas Micius (Evaldas Micius)
Original Redmine Issue: 9734
Affected QGIS version: 2.2.0
Redmine category:map_composer/printing


Adding rectangle or other shape (triangle, ellipse) causes constant high CPU usage (one core used 100%). High core usage causes save/open dialogs become unresponsive.
Possible source of bug might be related to Qt transparency parameters, because CPU usage drops to normal values as soon as object transparency is set to 100 (see screenshots).

Bug is also present in QGIS master, however it was not present in QGIS 2.0.

I'm running 2.2.0-2 QGIS on 32 bit version of Windows 7.
QGIS installed via OSGeo4W installer with no 3rd party plugins.


@qgib
Copy link
Contributor Author

qgib commented Mar 8, 2014

Author Name: Nyall Dawson (@nyalldawson)


I can't reproduce this. Is this on a blank project or do you only see it with a specific project?

Its possible the debug log may help - try downloading debugview from http://technet.microsoft.com/en-au/sysinternals/bb896647.aspx
Then run the current Dev version and start debugview (from memory you select something like enable global win32 from the menus to see qgis debug messages). Then reproduce this issue and see if anything is being printed to the log. If so, copy and paste it here for me.

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2014

Author Name: Evaldas Micius (Evaldas Micius)


I'm getting the bug on a blank project.

Updated to most recent dev version - the bug remains :(

If I draw a rectangle or any other shape on composer space and try to open any save/open dialog, e.g. "load template", a window pops up, but widgets fail to draw (screenshot attached). After a while widgets get drawn, however if I browse to some directory, file listings refresh only if I move the window. I guess it's related to high CPU usage, since with an empty composer canvas everything works fine.

The interesting part is that everything is OK while I draw the rectangle. I can mess around while in rubberband mode. but as soon as I release mouse - CPU usage hits the ceiling. If I delete the object, everything goes to normal.

Debug log doesn't seem to give any information. Attached it anyway (the part where the bug is and full log from application start).


  • 6964 was configured as full_log.txt
  • 6963 was configured as log.txt
  • 6962 was configured as Clipboard02.png

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2014

Author Name: Evaldas Micius (Evaldas Micius)


One more interesting detail - CPU drops to normal if I change blending mode of the rectangle to any other value besides "Normal". Resetting blending mode to normal causes the bug to reappear.

[Edit] Buggy behaviour disappears if I zoom to any empty region of the canvas where the rectangle is not visible.

@qgib
Copy link
Contributor Author

qgib commented Mar 25, 2014

Author Name: Nyall Dawson (@nyalldawson)


Can you please test again with the current 2.3 dev version? There's been a small change which may have fixed this issue.

@qgib
Copy link
Contributor Author

qgib commented Apr 1, 2014

Author Name: Nyall Dawson (@nyalldawson)


Fixed in changeset "2b3108f9aeadb6814ad0519b2c53840db2c834d1".


  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks Crash/Data Corruption labels May 24, 2019
@qgib qgib added this to the Version 2.2 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks
Projects
None yet
Development

No branches or pull requests

1 participant