Opened 2 years ago
Closed 22 months ago
#23405 closed defect (needinfo)
Problème de chargement d'imagerie provoquant un plantage de l'application.
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core imagery | Version: | |
| Keywords: | Bing | Cc: | sebastien.merle67@… |
Description
Bonjour,
Suite à un problème de chargement de l'imagerie aérienne Bing causé à cause d'un bloqueur de publicité chez moi, à provoqué une plantage de JOSM qui cesse de fonctionner (impossible à fermer et de faire n'importe quelque action).
Est-ce normal que l'application cesse de fonctionne, quand JOSM n'arrive pas à ouvrir une imagerie aérienne.
Attachments (0)
Change History (7)
follow-up: 3 comment:1 by , 2 years ago
| Component: | Core → Core imagery |
|---|---|
| Keywords: | Bing added |
comment:2 by , 2 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:3 by , 2 years ago
Eng :
I still have some memory space on my computer, though. I couldn't interact with JOSM.
I only had Bing aerial imagery open.
The fact that the Bing aerial imagery wouldn't open was because an ad blocker had blacklisted the Bing server.
Fr :
J'ai pourtant encore de l'espace mémoire sur mon ordinateur. Je n'avais pas la possibilité d'interagir avec JOSM.
J'avais d'ouvert seulement l'imagerie aérienne Bing.
Le fait que l'imagerie aérienne Bing ne s'ouvrait pas était à cause d'un bloqueur de publicité qui avait blackliste le serveur de Bing.
Replying to skyper:
Sounds like you ran out of memory. Does deleting another imagery layer work to free some memory?. In order to better understand the situation and possibly help you, we need more info, especially the status report, and the numbers of imagery layer open at that point and may be some coordinates.
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
- The required parts of the Status Report from your JOSM.
- Please, use
Report Bug from Help menu and copy & paste.
- Describe what behaviour you expected.
- Describe what did happen instead.
- Describe if and how the issue is reproducible.
- Add any relevant information like error messages or screenshots.
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help →
Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!
follow-up: 5 comment:4 by , 2 years ago
Thanks, sorry, I should read more carefully. So you are using Webstart and JOSM stalled downloading the imagery which was blocked. Instead it should timeout. Still, would you please add your status report as described above. Thanks a lot.
follow-up: 6 comment:5 by , 2 years ago
JOSM didn't give me a state report saying there was a problem. It no longer responded to any manipulation, and the only way to close it was to restart the computer.
Replying to skyper:
Thanks, sorry, I should read more carefully. So you are using Webstart and JOSM stalled downloading the imagery which was blocked. Instead it should timeout. Still, would you please add your status report as described above. Thanks a lot.
comment:6 by , 2 years ago
Replying to SUPER HEROS 67 / Sébastien <sebastien.merle67@…>:
JOSM didn't give me a state report saying there was a problem. It no longer responded to any manipulation, and the only way to close it was to restart the computer.
I understand that there was no status report generated as JOSM stalled. Are you using Webstart, some installer or even the .jar file directly? This and some other questions can be answered by the status report. So please, use the "Report Bug" action as described above just now and copy & past the status report. This would help a lot. Thank you.
comment:7 by , 22 months ago
| Resolution: | → needinfo |
|---|---|
| Status: | needinfo → closed |



Sounds like you ran out of memory. Does deleting another imagery layer work to free some memory?. In order to better understand the situation and possibly help you, we need more info, especially the status report, and the numbers of imagery layer open at that point and may be some coordinates.
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help →
Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!