kendzi / kendzi3d

3D plugin for JOSM
57 stars 19 forks source link

Latest JOSM freezes when using this plugin. #10

Open AaronAsAChimp opened 11 years ago

AaronAsAChimp commented 11 years ago

The latest version of JSOM (5697 and development version 5704) with the Kendzi3D plugin installed and set to auto start causes JSOM to freeze when using the menu.

Steps to reproduce:

  1. Install JSOM 5697 on Mac OSX.
  2. Ensure Look and Feel in the JSOM preferences is set to Mac OSX.
  3. Install the Kendzi3D 164
  4. Restart JOSM
  5. Open a menu (like Imagery)
  6. JSOM Fails to respond and requires a force quit.

Because JSOM preferences and plugins remain after uninstalling, JSOM is no longer functional.

Workaround:

  1. Download an older version JSOM (5608) http://josm.openstreetmap.de/download/
  2. In the 3D menu uncheck Plugin Autostart
  3. Resume using latest JOSM.
kendzi commented 11 years ago

I test it on windows and it work fine. How to setup Mac OSX Look and feel? Which OS are you using?

AaronAsAChimp commented 11 years ago

I'm using Mac OSX 10.8.2, I'm assuming the Mac Look and Feel is specific to the Mac version of java.

kendzi commented 11 years ago

Unfortunately I don't have access to Mac OSX. Can you test more precisely which JOSM patch between 5608 and 5697 cause the problem?

AaronAsAChimp commented 11 years ago

After testing a number of versions it doesn't seem to be related to the version but the type of build. All of the jars and the jnlp are affected (including 5608), but the macosx build is not.

dora71 commented 11 years ago

I can confirm a similar bug with Linux Mint 13 and Oracle Java 7 java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) Server VM (build 23.7-b01, mixed mode) I tested JOSM version 5577, 5608 and the latest stable version 5759, kendzi3d is fetched via JOSM from plugin section. JOSM does not start up any more as soon as the module begins to load. If needed, I can attach console output during startup. Didn't insert it here because it is quite a lot.

dora71 commented 11 years ago

Just wanted to add 3 warnings from console output, perhaps that's the clue already:

0 [main] WARN kendzi.josm.kendzi3d.service.impl.PointModelService - cant load point motel configuration from: /models/pointModelLayerInternal.xml url don't exist: jar:file:/home/rainer/.josm/plugins/kendzi3d.jar!/models/pointModelLayerInternal.xml reciveFileUrl: /home/rainer/.josm/plugins/kendzi3d/models/pointModelLayer.xml reciveFileUrl: /home/rainer/.josm/plugins/kendzi3d/resources/metadata.properties reciveFileUrl: /home/rainer/.josm/plugins/kendzi3d/textures/wikimetadata.properties 91 [main] WARN kendzi.josm.kendzi3d.service.MetadataCacheService - cant find url for file: /textures/wikimetadata.properties reciveFileUrl: /home/rainer/.josm/plugins/kendzi3d/resources/textureLibraryInternal.xml reciveFileUrl: /home/rainer/.josm/plugins/kendzi3d/resources/textureLibraryWiki.xml 112 [main] WARN kendzi.josm.kendzi3d.service.TextureLibraryService - cant load texture configuration from: /resources/textureLibraryWiki.xml url don't exist: jar:file:/home/rainer/.josm/plugins/kendzi3d.jar!/resources/textureLibraryWiki.xml

Hope this helps in some way.

kendzi commented 11 years ago

dora71: please check it with josm version 5796 http://josm.openstreetmap.de/ticket/8533

kendzi commented 11 years ago

AaronAsAChimp, do I understand correctly that mac release is always working and "normal" release is not? normal release: http://josm.openstreetmap.de/download/ macosx release: http://josm.openstreetmap.de/download/macosx/

dora71 commented 11 years ago

kendzi: Plugin works fine with JOSM version 5801, thanks for quick answer and solution. Tested with Debian sid, Java Version 1.7.0_17

AaronAsAChimp commented 11 years ago

I can only explain it as some type of threading problem. I don't know if your plugin or JOSM is multithreaded, but its the closest parallel I can draw.

I've seen these types of problems (with other Java applications) happen on one machine consistently but not others even with identical specs. If it is a threading issue, it dosen't surprise me at all different builds have slightly different timings, and as a result one breaks and the other doesn't.