Parallel multi-core rendering glitches with OTF reprojection #19717

qgib · 2014-10-19T01:23:20Z

Author Name: Anita Graser (@anitagraser)
Original Redmine Issue: 11441
Affected QGIS version: master
Redmine category:map_canvas

With active on-the-fly reprojection and parallel rendering, the map renders with big artifacts. I've tested the following project with both the 2.4 release and today's nightly:

https://github.com/FOSS4GAcademy/GST101FOSS4GLabs/tree/master/Module%204%20Lab/QGIS%202.2/Lab%204%20Data

Deactivating either OTF or parallel rendering fixes the problem as far as I can tell.

!glitch.png!

glitch.png (Anita Graser)
projissues.PNG (Anita Graser)
glitch219.PNG (Anita Graser)

Related issue(s): #19979 (relates)
Redmine related issue(s): 11746

qgib · 2014-10-19T03:15:34Z

Author Name: Giovanni Manghi (@gioman)

cannot confirm here, tested on master on both Linux and Windows (same project and data).

status_id was changed from Open to Feedback

qgib · 2014-10-19T07:09:22Z

Author Name: Gary Sherman (@g-sherman)

Try turning off simplification and/or "Make lines appear less jagged..." and see if it goes away. We had a similar problem years ago and I don't recall the root cause.

qgib · 2014-10-19T09:26:19Z

Author Name: Saber Razmjooei (@saberraz)

There are layers from outside the OTF CRS. According to this website: http://prj2epsg.org/epsg/5070 Canada and Mexico are outside EPSG:5070's CRS zone. I guess this causes the problem.

I have removed Mexico and Canada and the problem seems to have disappeared.

qgib · 2014-10-19T10:19:49Z

Author Name: Anita Graser (@anitagraser)

@gary: Changing the simplification settings (values, on/off) or deactivating anti-aliasing didn't change the results.

@saber: Even if I only use the US states (which should be within the CRS zone), these artifacts appear.

qgib · 2014-10-19T23:06:50Z

Author Name: Saber Razmjooei (@saberraz)

It has become less frequent. To completely get rid of the problem, I saved western_states in 5070 and used that instead. But that does not explain the source of problem.

qgib · 2014-10-20T00:22:00Z

Author Name: Martin Dobias (@wonder-sk)

I cannot replicate the problem.

@anita / @saber - which version of Proj.4 do you use? Does it happen also if you use a wgs84 for destination CRS? To my (brief) knowledge, the used epsg 5070 uses a grid file. Could you try some other projection for north america that does not involve reading of grid files? (based on parameters only)

Apparently the proj library versions < 4.8 were prone to errors when used in multi-threaded environment, but maybe we should also make use of contexts introduced in 4.8:
https://trac.osgeo.org/proj/wiki/ThreadSafety

qgib · 2014-10-20T00:37:56Z

Author Name: Giovanni Manghi (@gioman)

Martin Dobias wrote:

I cannot replicate the problem.

@anita / @saber - which version of Proj.4 do you use? Does it happen also if you use a wgs84 for destination CRS? To my (brief) knowledge, the used epsg 5070 uses a grid file. Could you try some other projection for north america that does not involve reading of grid files? (based on parameters only)

Apparently the proj library versions < 4.8 were prone to errors when used in multi-threaded environment, but maybe we should also make use of contexts introduced in 4.8:
https://trac.osgeo.org/proj/wiki/ThreadSafety

it seems anyway strange to me as I tested also on Windows (where anyone should have the same libraries) and cannot replicate the issue.

qgib · 2014-10-20T00:56:28Z

Author Name: Martin Dobias (@wonder-sk)

Giovanni Manghi wrote:

it seems anyway strange to me as I tested also on Windows (where anyone should have the same libraries) and cannot replicate the issue.

Unfortunately this is not that strange. It is quite common that errors in multi-threaded code appear just for some people, while working flawlessly for others.

qgib · 2014-10-20T01:56:33Z

Author Name: Saber Razmjooei (@saberraz)

It works fine in both WGS84 and 4269.

qgib · 2014-11-22T09:14:13Z

Author Name: Giovanni Manghi (@gioman)

still true?

qgib · 2014-11-22T12:34:19Z

Author Name: Anita Graser (@anitagraser)

Still true for me (Win8 OSGeo4W nightly 64bit).

qgib · 2015-05-10T23:46:46Z

Author Name: Giovanni Manghi (@gioman)

status_id was changed from Feedback to Open

qgib · 2015-05-11T07:53:56Z

Author Name: Anita Graser (@anitagraser)

Still true for 2.8.1 (Win8 OSGeo4W 64bit).

qgib · 2015-10-11T07:14:12Z

Author Name: Anita Graser (@anitagraser)

Still true for 2.11 today.

fixed_version_id was configured as Future Release - High Priority

qgib · 2016-01-23T08:58:53Z

Author Name: Martin Dobias (@wonder-sk)

As far as I can tell from my tests, this problem was caused by a bug in proj.4 library: OSGeo/PROJ#226

It has been fixed in proj 4.9.2 (released Sep 2015) which is now also available in osgeo4w (since end of Nov 2015). Could you please test again with the latest proj4 version to see if the problem is gone?

status_id was changed from Open to Feedback

qgib · 2016-01-23T09:32:08Z

Author Name: Anita Graser (@anitagraser)

Unfortunately still around ... even with the new proj ..

!projissues.PNG!

Please put back to "open".

9494 was configured as projissues.PNG

projissues.PNG (Anita Graser)

qgib · 2016-03-04T00:02:10Z

Author Name: Anita Graser (@anitagraser)

@martin Can you please change the status back to open? Thanks!

qgib · 2016-03-04T00:04:46Z

Author Name: Martin Dobias (@wonder-sk)

Maybe we can have a look at it in Girona...

status_id was changed from Feedback to Open

qgib · 2017-01-08T23:42:17Z

Author Name: Giovanni Manghi (@gioman)

is there any update on this issue?

status_id was changed from Open to Feedback

qgib · 2017-01-09T10:12:40Z

Author Name: Anita Graser (@anitagraser)

Still same error unfortunately. Tested with latest 2.19 in OSGeo4W - so not latest master

!glitch219.PNG!

10653 was configured as glitch219.PNG

glitch219.PNG (Anita Graser)

qgib · 2017-01-10T03:40:48Z

Author Name: Jürgen Fischer (@jef-n)

Anita Graser wrote:

so not latest master

not even master - qgis-dev is from (removed) master_2. qgis-rel-dev should be more up to date (branched off from master_2 on release of 2.18)

qgib · 2017-01-10T04:17:17Z

Author Name: Giovanni Manghi (@gioman)

Jürgen Fischer wrote:

Anita Graser wrote:

so not latest master

not even master - qgis-dev is from (removed) master_2. qgis-rel-dev should be more up to date (branched off from master_2 on release of 2.18)

There will ever be a master/qgis3 package on osgeo4w? Just a practical question: I do/did most of master testing on Windows because it was very practical, if there will be no more master on osgeo4w I will have to review my strategy and compile daily on Linux.

status_id was changed from Feedback to Open

qgib · 2017-01-10T04:40:00Z

Author Name: Jürgen Fischer (@jef-n)

Giovanni Manghi wrote:

There will ever be a master/qgis3 package on osgeo4w?

sure.

qgib · 2017-01-10T06:56:09Z

Author Name: Anita Graser (@anitagraser)

Jürgen Fischer wrote:

qgis-rel-dev should be more up to date (branched off from master_2 on release of 2.18)

Ok, I'll try with qgis-rel-dev

qgib · 2017-01-10T08:09:07Z

Author Name: Anita Graser (@anitagraser)

Same issue in qgis-rel-dev

qgib · 2017-03-06T14:04:14Z

Author Name: Giovanni Manghi (@gioman)

Anita Graser wrote:

Same issue in qgis-rel-dev

what about the (qgis3) master? any change?

version was changed from master to 2.18.4
status_id was changed from Open to Feedback
priority_id was changed from High to Normal
fixed_version_id removed Future Release - High Priority

qgib · 2017-03-07T13:42:49Z

Author Name: Anita Graser (@anitagraser)

Still same here with 2.99 from OSGeo4W.

qgib · 2017-03-07T23:20:47Z

Author Name: Giovanni Manghi (@gioman)

fixed_version_id was configured as Version 3.0
status_id was changed from Feedback to Open
version was changed from 2.18.4 to master

qgib · 2017-04-30T23:07:44Z

Author Name: Giovanni Manghi (@gioman)

regression was configured as 0
easy_fix was configured as 0

qgib · 2017-05-17T18:36:42Z

Author Name: Nyall Dawson (@nyalldawson)

Anita - please test the next nightly 3.0 release as this is likely fixed now.

status_id was changed from Open to Feedback
description was changed from With active on-the-fly reprojection and parallel rendering, the map renders with big artifacts. I've tested the following project with both the 2.4 release and today's nightly:

https://github.com/FOSS4GAcademy/GST101FOSS4GLabs/tree/master/Module%204%20Lab/QGIS%202.2/Lab%204%20Data

Deactivating either OTF or parallel rendering fixes the problem as far as I can tell.

!glitch.png! to With active on-the-fly reprojection and parallel rendering, the map renders with big artifacts. I've tested the following project with both the 2.4 release and today's nightly:

https://github.com/FOSS4GAcademy/GST101FOSS4GLabs/tree/master/Module%204%20Lab/QGIS%202.2/Lab%204%20Data

Deactivating either OTF or parallel rendering fixes the problem as far as I can tell.

!glitch.png!

qgib · 2017-11-13T00:41:22Z

Author Name: Nyall Dawson (@nyalldawson)

Anita -can we close this? Should be fixed in master and recent 2.18

qgib · 2017-11-13T16:49:31Z

Author Name: Anita Graser (@anitagraser)

Looks good! Thanks Nyall!

status_id was changed from Feedback to Closed
resolution was changed from to fixed/implemented

qgib closed this as completed Nov 13, 2017

qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Map and Legend Related to map or legend rendering labels May 25, 2019

qgib added this to the Version 3.0 milestone May 25, 2019

This was referenced May 25, 2019

[Composer Legend] Symbology of layer always follows the map canvas and breaks the composer legend #24694

Closed

Vertical lines appear as artifacts when map has lots of layers turned on. #19979

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Parallel multi-core rendering glitches with OTF reprojection #19717

Parallel multi-core rendering glitches with OTF reprojection #19717

qgib commented Oct 19, 2014 •

edited

Loading

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 20, 2014

qgib commented Oct 20, 2014

qgib commented Oct 20, 2014

qgib commented Oct 20, 2014

qgib commented Nov 22, 2014

qgib commented Nov 22, 2014

qgib commented May 10, 2015

qgib commented May 11, 2015

qgib commented Oct 11, 2015

qgib commented Jan 23, 2016

qgib commented Jan 23, 2016

qgib commented Mar 4, 2016

qgib commented Mar 4, 2016

qgib commented Jan 8, 2017

qgib commented Jan 9, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Mar 6, 2017

qgib commented Mar 7, 2017

qgib commented Mar 7, 2017

qgib commented Apr 30, 2017

qgib commented May 17, 2017

qgib commented Nov 13, 2017

qgib commented Nov 13, 2017

Parallel multi-core rendering glitches with OTF reprojection #19717

Parallel multi-core rendering glitches with OTF reprojection #19717

Comments

qgib commented Oct 19, 2014 • edited Loading

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 19, 2014

qgib commented Oct 20, 2014

qgib commented Oct 20, 2014

qgib commented Oct 20, 2014

qgib commented Oct 20, 2014

qgib commented Nov 22, 2014

qgib commented Nov 22, 2014

qgib commented May 10, 2015

qgib commented May 11, 2015

qgib commented Oct 11, 2015

qgib commented Jan 23, 2016

qgib commented Jan 23, 2016

qgib commented Mar 4, 2016

qgib commented Mar 4, 2016

qgib commented Jan 8, 2017

qgib commented Jan 9, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Jan 10, 2017

qgib commented Mar 6, 2017

qgib commented Mar 7, 2017

qgib commented Mar 7, 2017

qgib commented Apr 30, 2017

qgib commented May 17, 2017

qgib commented Nov 13, 2017

qgib commented Nov 13, 2017

qgib commented Oct 19, 2014 •

edited

Loading