You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Tony Walters (@tonywsea)
Original Redmine Issue: 19714
Affected QGIS version: 3.2.2
Redmine category:rasters
Often, but not always the system hangs locking the GUI. This can last a minute or more. It may happen in other situations, but I can verify that a raster file I created from IDM interpolation will cause this condition. The file size of the raster is about 750k. The system is more stable when opacity slider is removed.
Whether the opacity slider is on or off, I notice that my I7 two physical core/4 logical core PC shows all 4 cores heavy processing during this period of unresponsiveness no matter whether I set rendering to 4 cores, or many cores, or turn off multi-core rendering altogether. This symptom also exhibits itself in 3.0 installation, but seems worse in 3.2.2
Bulk closing 82 tickets in feedback state for more than 90 days affecting an old version. Feel free to reopen if it still applies to a current version and you have more information that clarify the issue.
qgib
added
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Rasters
Related to general raster layer handling (not specific data formats)
labels
May 25, 2019
Author Name: Tony Walters (@tonywsea)
Original Redmine Issue: 19714
Affected QGIS version: 3.2.2
Redmine category:rasters
Often, but not always the system hangs locking the GUI. This can last a minute or more. It may happen in other situations, but I can verify that a raster file I created from IDM interpolation will cause this condition. The file size of the raster is about 750k. The system is more stable when opacity slider is removed.
Whether the opacity slider is on or off, I notice that my I7 two physical core/4 logical core PC shows all 4 cores heavy processing during this period of unresponsiveness no matter whether I set rendering to 4 cores, or many cores, or turn off multi-core rendering altogether. This symptom also exhibits itself in 3.0 installation, but seems worse in 3.2.2
The text was updated successfully, but these errors were encountered: