Modify

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#4289 closed defect (fixed)

rendering goes crazy at high zoom levels

Reported by: nelson@… Owned by: team
Priority: normal Component: Core
Version: latest Keywords: painting java clipping
Cc: skyper

Description

Extreme zoom levels (<1M) cause the painting to go crazy, drawing pie-shaped fills out to the edge of the screen. Present in 2255, but I don't recall it being present in 0.5 versions of JOSM. Sometimes it's necessary to zoom in that far to be able to select just one node very close to another node.

Attachments (5)

josm_bug_4289.osm.bz2 (117.6 KB) - added by skyper 3 years ago.
osm
screenshot_1m.png (147.5 KB) - added by skyper 3 years ago.
screenshot_under_1m.png (128.9 KB) - added by skyper 3 years ago.
screenshot_1m_2.png (127.1 KB) - added by skyper 3 years ago.
better screenshot still same area
screenshot_under_1m_2.png (108.8 KB) - added by skyper 3 years ago.
better screenshot still same area

Download all attachments as: .zip

Change History (16)

comment:1 Changed 3 years ago by stoecker

  • Owner changed from team to nelson@…
  • Status changed from new to needinfo

Probably related to #4040 (there GPX). It seems the draw functions go berserk when to much stuff is drawn outside the visible area. Could you a add screenshots and probably provide a reproducable description including data file.

comment:2 Changed 3 years ago by skyper

  • Owner changed from nelson@… to team
  • Status changed from needinfo to new
  • Summary changed from drawing goes crazy at high zoom levels to rendering goes crazy at high zoom levels
  • Version set to latest

This bug exists for some time now.
Sometimes rendering goes crazy at high zoom levels, not rendering all the objects and changing colors. Sometimes you only see nodes but no ways and more.

The screenshot looks quite different than the one from #4040.
Sorry I did not get a nice screenshot, but I try to get more.
Pictures are taken in the lower right edge.

cu skyper

Changed 3 years ago by skyper

osm

Changed 3 years ago by skyper

Changed 3 years ago by skyper

comment:3 Changed 3 years ago by skyper

Funny, trying to get the second screenshots the background changed back to black in some areas. I think it is the background color thats the problem speaking for myself.

Changed 3 years ago by skyper

better screenshot still same area

Changed 3 years ago by skyper

better screenshot still same area

comment:4 Changed 3 years ago by skyper

  • Cc skyper added

comment:5 follow-up: Changed 3 years ago by bastiK

Still cannot reproduce. Could not find the place of the first screenshot in the data file.
Does it happen each time you zoom < 1m or is it only under certain conditions?

You have 2 data layers, one inactive. Does this also happen if you have only one layer?

Do you use Sun Java? What version?

Sorry for all the questions, but it is very hard to debug if you cannot reproduce the problem.

comment:6 in reply to: ↑ 5 ; follow-up: Changed 3 years ago by skyper

Replying to bastiK:

Still cannot reproduce. Could not find the place of the first screenshot in the data file.
Does it happen each time you zoom < 1m or is it only under certain conditions?

  1. one is from the intersection a bit left of the second one. Look for highway=crossing with no connection.

Yes it happens all the time, sometimes disappearing and then reappearing again.

You have 2 data layers, one inactive. Does this also happen if you have only one layer?

Yes

Do you use Sun Java? What version?

No, debian squeeze (openjdk-6b17~pre3-1)

Sorry for all the questions, but it is very hard to debug if you cannot reproduce the problem.

No problem. You were lucky to reach me! I am offline for the weekend.
cu next week Skyper

comment:7 in reply to: ↑ 6 Changed 3 years ago by bastiK

Do you use Sun Java? What version?

No, debian squeeze (openjdk-6b17~pre3-1)

Then it's probably another flavor of #3313. Maybe roundoff error involved?

comment:8 Changed 3 years ago by bastiK

I could confirm this for openjdk. The cause seems to be the same openjdk bug as in #3313. A fix for this would be to clip each segment before it gets painted.

However I'm not sure if this would have any performance impact. Maybe we can do a workaround for openjdk users only. (One can check System.getProperty("java.vm.name") for this.)

comment:9 Changed 3 years ago by nelson@…

I can confirm that the problem is present only with openjdk.

comment:10 Changed 3 years ago by bastiK

  • Resolution set to fixed
  • Status changed from new to closed

(In [2987]) fixed #4289 - rendering goes crazy at high zoom levels,
fixed #4424 - Problems rendering long ways at higher zoom levels

comment:11 Changed 3 years ago by stoecker

  • Keywords painting java clipping added

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.