Author: Richard
[Added to the original trac issue at 2.34pm, Tuesday, 15th March 2011]

Please provide exact steps to reproduce:

• Permalink of area on osm.org where this happens
• Way IDs that you're trying to merge
• Click/keypress sequence that you follow to cause the crash
• Version of Flash Player you are using

Author: FK270673
[Added to the original trac issue at 4.24pm, Tuesday, 15th March 2011]

• http://www.openstreetmap.org/?lat=39.58766&lon=-81.69496&zoom=15&layers=M
• about 10 pieces of power line, after the 10th piece it got a little bit slow and the advanced tab didn't reload correctly
• "couldn't load map" button appeared
• either clicking (X) button after tiger:id or trying to rename tiger:id from "XYZ:XYZ" to "_"
• You have version 10,2,152,26 installed

Author: Richard
[Added to the original trac issue at 4.49pm, Tuesday, 15th March 2011]

Ok, so the issue appears to be that P2 is not coping with very long key or value strings. I can't actually reproduce it but that doesn't matter, as we shouldn't be allowing strings of over 255 characters anyway - they'll cause an API error on upload.

Summary changed; priority demoted from 'blocker' as P2 does actually show a warning (albeit a fairly ugly long one!) about tag mismatches when merging ways, and you should heed it. :)

Author: FK270673
[Added to the original trac issue at 2.19pm, Thursday, 17th March 2011]

Today, it crashed again while editing the (TIGER) tabs of an existing power line (11837892) with Potlatch2. I tried to remove the tiger:tlid=51137899:51137901:51137903:51137905 manually when Potlatch2 crashed.

There must be an error with loading/reloading/editing properties while Potlatch2 is being busy - far before the saving error appears.

It would be fine if these funny numbers would disappear from the database rather than causing my editor to crash.

Author: Richard
[Added to the original trac issue at 2.25pm, Thursday, 17th March 2011]

Unfortunately your previous comment wasn't exact enough for me to be able to reproduce it, and if we can't reproduce it we can't fix it.

If, as requested originally, you could provide an exact'' series of actions, we can look at it as a matter of urgency. But "about 10 pieces of power line" - what are you doing with these power lines? How, ''exactly, are you doing it?

Please don't reverse the developers' classification of priorities; thanks. By definition if only one person has encountered the problem then it isn't something we would consider a blocker.

Author: FK270673
[Added to the original trac issue at 4.30pm, Thursday, 17th March 2011]

Unfortunately, these critical errors seem to be a result of multiple conditions.

• 1. Choose a time when Potlatch2 is reloading slowly
• 2. Use the ADVANCED tab as it is a good indicator for a pre-crash situation
• 3. Draw a very long line, e.g. a powerline, until you reach an area that does not reload quickly.
• 4. Add some / many pylons there (with R), you may edit some other nodes and ways as well. For TESTING purposes, it is a good idea to tag every SECOND node as pylon an to leave the other one blank, so you can see whether the ADVANCED tab indicates all changes between blank and tagged nodes correctly.
• 5. If the ADVANCED tab remains EMPTY or keeps the properties of the PREVIOUS edit though you have added a pylon (with R), you have reached the stage two steps BEFORE the crash happened (!!).
• 6. The SIMPLE tab indicates the CORRECT tag WHILE the ADVANCED tab indicates the PREVIOUS tag. This is the condition BEFORE a CRASH - it works fine for 10 or 15 times, but then the editor crashes.
• 7. By adding a NEW TAG to the ADVANCED tab, e.g. ref=111, you may restore the CORRECT properties of that node / way. It works fine for 10 or 15 times, but then the editor CRASHES.
• 8. Manually removing a tigerID has caused the CRASH.

I suppose there must be a conflict between listeners, maybe the tab listener and some other reloading listener.

Author: FK270673
[Added to the original trac issue at 6.36am, Saturday, 2nd April 2011]

This time, Potlatch2 crashed in a reproducable way when I tried to join four highways in the United States with different TIGER IDs. Then, I tried to edit their combined ID manually with the Advanced Tab which caused the crash.

Author: Richard
[Added to the original trac issue at 1.20pm, Monday, 4th April 2011]

Both the "tag panel freezing" and the ">255 characters" issues should now have been fixed. I'd be interested to know whether this solves your problem.

Author: Richard
[Added to the original trac issue at 6.11pm, Saturday, 7th May 2011]

No further reports on this so I'm assuming it's been fixed: please reopen if not.