Opened 2 years ago
Last modified 12 months ago
#6284 new defect
Upon opening JOSM encountered error message
| Reported by: | cropper_1@… | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | tested | Keywords: | template_report |
| Cc: |
Description (last modified by kolen)
What steps will reproduce the problem?
- Simply opening JOSM, I did however have another java application I'm developing running in the background
What is the expected result?
For the JOSM to load normally, with the progress bar
What happens instead?
The error message below was presented to me
Please provide any additional information below. Attach a screenshot if
possible.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2011-04-14 01:31:50 Last Changed Author: bastiK Revision: 4021 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2011-04-13 22:43:46 +0200 (Wed, 13 Apr 2011) Last Changed Rev: 4021 Identification: JOSM/1.5 (4021 en_GB) Memory Usage: 30 MB / 494 MB (10 MB allocated, but free) Java version: 1.6.0_24, Sun Microsystems Inc., Java HotSpot(TM) Client VM Operating system: Windows 7 Plugin: openstreetbugs (25664) Plugin: turnrestrictions (25845) java.lang.IndexOutOfBoundsException: Index: 3, Size: 3 at java.util.ArrayList.RangeCheck(Unknown Source) at java.util.ArrayList.get(Unknown Source) at java.awt.Container.createHierarchyEvents(Unknown Source) at java.awt.Container.createHierarchyEvents(Unknown Source) at java.awt.Container.createHierarchyEvents(Unknown Source) at java.awt.Container.createHierarchyEvents(Unknown Source) at java.awt.Container.createHierarchyEvents(Unknown Source) at java.awt.Container.createHierarchyEvents(Unknown Source) at java.awt.Component.hide(Unknown Source) at java.awt.Window.hide(Unknown Source) at java.awt.Component.show(Unknown Source) at java.awt.Component.setVisible(Unknown Source) at java.awt.Window.setVisible(Unknown Source) at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:228
Attachments (0)
Change History (13)
comment:1 Changed 2 years ago by bastiK
comment:2 Changed 2 years ago by anonymous
Well all I can really say in terms of reproducing this issue, I was developing a Java program at the time and was in the debug stages
comment:3 Changed 2 years ago by stoecker
Ticket #6289 has been marked as a duplicate of this ticket.
comment:4 Changed 2 years ago by stoecker
Maybe somehow caused by the changes in the program icon? Probably the Java function for multiple icons is buggy?
comment:5 Changed 2 years ago by cropper_1@…
Possibly, I mean the program I'm devloping does involve icon's as well
comment:6 Changed 2 years ago by jttt
Exceptions like this sometimes happen when gui is accessed from non EDT thread. Check http://weblogs.java.net/blog/alexfromsun/archive/2006/02/debugging_swing.html for ways to detect EDT rules violations (ThreadCheckingRepaintManager is imho sufficient).
In this case, most of code in MainApplication.main should be executed inside of EventQueue.invokeLater(), not directly in main thread.
comment:7 Changed 2 years ago by stoecker
Ticket #5882 has been marked as a duplicate of this ticket.
comment:8 Changed 21 months ago by skyper
Ticket #6931 has been marked as a duplicate of this ticket.
comment:9 follow-up: ↓ 13 Changed 20 months ago by kolen
- Description modified (diff)
Occured today when using reverter plugin, after downloading objects needed to revert.
Stacktrace: https://gist.github.com/1325761
comment:10 Changed 19 months ago by Don-vip
Ticket #7112 has been marked as a duplicate of this ticket.
comment:11 Changed 19 months ago by Don-vip
Ticket #5040 has been marked as a duplicate of this ticket.
comment:12 Changed 13 months ago by skyper
- Priority changed from normal to major
comment:13 in reply to: ↑ 9 Changed 12 months ago by simon04
Replying to kolen:
Occured today when using reverter plugin, after downloading objects needed to revert.
Stacktrace: https://gist.github.com/1325761
Fixed in r4761.
I'm not sure whether (different) stacktraces from #6284=#7112 are still relevant.



Looks more like a Java bug of some kind, can you reproduce?