Opened 11 months ago

Closed 2 weeks ago

#17971 closed defect (fixed)

completely stall of program

Reported by: skyper Owned by: jpietri
Priority: critical Milestone:
Component: Plugin mapillary Version: latest
Keywords: template_report stall Cc:


What steps will reproduce the problem?

Simple editing with mapillary layer active.

What is the expected result?

Normal run of the program.

What happens instead?

completely stall of program

Please provide any additional information below. Attach a screenshot if possible.

Do not exactly know what causes this problem but I blame either mapillary or download mechanism of imagery, as it did only a cure so far with an active mapillary layer and once after enabling Bing and the connection broke before the attribution was downloaded.

Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-07-23 21:47:40 +0200 (Tue, 23 Jul 2019)
Build-Date:2019-07-24 01:30:51
Relative:URL: ^/trunk

+ ElevationProfile (35066)
+ ImportImagePlugin (34908)
+ Mapillary (1.5.18)
+ apache-commons (34908)
+ apache-http (34908)
+ ejml (35049)
+ geotools (34908)
+ imagery_offset_db (34908)
+ jaxb (35014)
+ jna (34908)
+ jts (35064)
+ log4j (34908)
+ opendata (34997)
+ reverter (34999)
+ tag2link (35070)
+ undelete (34977)
+ utilsplugin2 (34977)

Do not get through the spam filter with console output and dump (too many links). Gonna attach them.

Attachments (1)

log.tar.xz (15.1 KB) - added by skyper 11 months ago.
console log and dump (hope I get through spam filter)

Download all attachments as: .zip

Change History (24)

Changed 11 months ago by skyper

Attachment: log.tar.xz added

console log and dump (hope I get through spam filter)

comment:1 Changed 11 months ago by skyper

2019-07-26 16:57:32.681 INFO: GET (get number of unread messages) -> HTTP_1 200 (462 B)
2019-07-26 17:02:32.705 INFO: GET (get number of unread messages) -> HTTP_1 200 (462 B)

Oh maybe it is only the unread messages task. Remember that I had problems with it years ago.

comment:2 Changed 10 months ago by naoliv

Maybe the problem is on this blocked thread?

"pool-4-thread-2" #1594 prio=5 os_prio=0 tid=0x00007f25980f9000 nid=0x3925 waiting for monitor entry [0x00007f258962c000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at java.awt.Component.enable(
        - waiting to lock <0x00000000ce82e5c0> (a java.awt.Component$AWTTreeLock)
        at javax.swing.JComponent.enable(
        at java.awt.Component.enable(
        at java.awt.Component.setEnabled(
        at javax.swing.JComponent.setEnabled(
        at javax.swing.AbstractButton.setEnabled(
        at org.openstreetmap.josm.gui.SideButton.setEnabled(
        at org.openstreetmap.josm.plugins.mapillary.MapillaryLayer.updateNearestImages(
        - locked <0x00000000dcfc77a8> (a org.openstreetmap.josm.plugins.mapillary.MapillaryLayer)
        at org.openstreetmap.josm.plugins.mapillary.MapillaryLayer.imagesAdded(
        at org.openstreetmap.josm.plugins.mapillary.MapillaryData$$Lambda$919/551601625.accept(Unknown Source)
        at java.util.Spliterators$ArraySpliterator.forEachRemaining(
        at org.openstreetmap.josm.plugins.mapillary.MapillaryData.fireImagesAdded(
        at org.openstreetmap.josm.plugins.mapillary.MapillaryData.addAll(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

comment:3 Changed 10 months ago by skyper

#17864 seems to be similar.

Last edited 10 months ago by skyper (previous) (diff)

comment:4 Changed 10 months ago by Don-vip

Component: CorePlugin mapillary
Owner: changed from team to jpietri

comment:5 Changed 10 months ago by richlv

This seems to be terribly easy to trigger lately. With automatic Mapillary image download enabled, I'm unable to pan the map view without getting a hang very soon.

comment:6 Changed 7 months ago by Don-vip

@richlv @naoliv @skyper do you still have this issue with Mapillary plugin 1.5.20?

comment:7 Changed 7 months ago by Don-vip

Ticket #17864 has been marked as a duplicate of this ticket.

comment:8 Changed 7 months ago by Don-vip

Steps to reproduce from #17864:

Here are steps that so far reproduce the hang pretty reliably for me with Mapillary downloads set to manual:

  • Download data in some area with Mapillary images.
  • Add Mapillary layer (shift+,).
  • Download Mapillary images (shift+.).
  • Select/open a Mapillary image.
  • Open Mapillary filtering and set it to show images, not older than one day (so that the currently displayed image is not show on the map).
  • Download Mapillary images again (shift+.).

Note that the last step might require panning/zooming a bit, before the download is initiated.

comment:9 Changed 7 months ago by richlv

Yep, got it easy to hang still.

comment:10 Changed 7 months ago by Don-vip

OK thanks. @jpietri did you start to look on this one?

comment:11 Changed 7 months ago by anonymous

I had a look at it some times ago @Don-vip. I could reproduce it from time to time. But unfortunately, I could not spot the issue, and I won't be able to investigate further on until the end of this year.
The possibly involved code (image download) is on both sides: the Mapillary plugin and some superclasses in JOSM core.

comment:12 Changed 6 months ago by mueschel

I have similar issues here.
Mapillary works well, unless I delete a data layer and create a new one:

  • open JOSM, download some data, add Mapillary layer - everything works, even for hours, additional downloads and panning are no problem
  • delete data layer, download some new data - JOSM freezes after few seconds, before any Mapillary information is shown

Identification: JOSM/1.5 (15492 en) Linux Ubuntu 19.04
Memory Usage: 439 MB / 2984 MB (162 MB allocated, but free)
Java version: 11.0.2+9-LTS, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM

Last edited 6 months ago by mueschel (previous) (diff)

comment:13 Changed 5 months ago by richlv

Unfortunately, this still happens with the latest JOSM+plugins version.

comment:14 Changed 4 months ago by richlv

Still happens with latest tested JOSM and latest plugins.

comment:15 Changed 4 weeks ago by taylor.smock

I think I fixed this in , so Mapillary v1.5.21+ (April 07, 2020) should have the fix.

@richlv/@skyper/@mueschel: Can any of you still reproduce this issue?

comment:16 Changed 4 weeks ago by mueschel

In the last weeks I was using v1.5.20 / JOSM 16239 (only today I upgraded to v1.5.22) and had the impression that this bug didn't appear anymore since at least one month. So, the bug seems to be gone at least on my installation, but not related to v1.5.21.

comment:17 Changed 4 weeks ago by richlv

I've developed a habit of not using Mapillary images in JOSM that much, thus cannot say for sure - but haven't had a hang like that recently. Will use it a bit more.
Thank you for all the updates to the plugin :)

comment:18 Changed 4 weeks ago by taylor.smock

@richlv: If you have a specific issue with the Mapillary plugin, a bug report would be appreciated. It might not be something I can work on for awhile, but at least I'll know its a problem.

comment:19 Changed 3 weeks ago by richlv

Sounds great - is Trac here still the preferred location for reporting things?

comment:20 Changed 3 weeks ago by taylor.smock

I have a feed set up for JOSM trac which I go through looking for bugs. I haven't set up the equivalent for GitHub, but I'm not the only developer for the Mapillary plugin. I prefer JOSM trac over Github issues, personally, but other devs may have different perspectives.

I try to look at both, but I may forget about checking Github issues for a week or two.

So, to answer your question, I don't know (for the Mapillary plugin). I just know I check JOSM trac, and occasionally look at Github Issues.

comment:21 Changed 2 weeks ago by taylor.smock

Ticket #18656 has been marked as a duplicate of this ticket.

comment:22 Changed 2 weeks ago by taylor.smock

Ticket #18704 has been marked as a duplicate of this ticket.

comment:23 Changed 2 weeks ago by taylor.smock

Resolution: fixed
Status: newclosed

I'm closing #17971, #18656, and #18704. I'm confident enough that the problem is actually fixed, and none of the ticket reports have indicated that it is still a problem.

See e1710fce8a5a5656d646a7a162554b540fa1fb4b for more details.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain jpietri.
as The resolution will be set.
The resolution will be deleted.

Add Comment

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

Note: See TracTickets for help on using tickets.