Modify

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#3796 closed defect (fixed)

JOSM lockup when loading duplicate data

Reported by: framm Owned by: hansendc
Priority: normal Component: Core
Version: latest Keywords:
Cc:

Description

JOSM (latest - 2328) freezes in the "preparing data set..." stage, emitting lots of

can not split, but too deep: 23 size: 19

messages on the console. This happens when I try to load the following URL:

GET http://api.openstreetmap.org/api/0.6/map?bbox=103.83873242862792,13.368442260419624,103.86928061454346,13.394550303033487

The data in this area is broken, seven identical imports have been made on top of each other.

PLEASE DO NOT FIX THE DATA, this is being looked after already; it's just that JOSM should handle this gracefully. (Maybe something else is wrong with the data - loading a small section of it does work, just the whole thing doesn't.)

I am attaching a saved version of the above data; the lock-up also happens when opening the file.

Attachments (1)

broken.osm.gz (225.7 KB) - added by framm 4 years ago.
data file that breaks josm

Download all attachments as: .zip

Change History (4)

Changed 4 years ago by framm

data file that breaks josm

comment:1 Changed 4 years ago by stoecker

  • Owner changed from team to hansendc

The message comes from QuadBuckets code.

comment:2 Changed 4 years ago by hansendc

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

(In [2423]) This fixes #3796.

The issue was that we somehow ended up with a branch node
that had no valid children. We assumed in the iterator
that any node with no content must have children, but
that was wrong.

comment:3 Changed 4 years ago by anonymous

Thanks for providing the trouble data. It helped finding the bug immensely.

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.