Modify

Opened 11 years ago

Closed 11 years ago

#11323 closed defect (irreproducible)

JOSM slow GUI

Reported by: germano Owned by: germano
Priority: normal Milestone:
Component: Core Version:
Keywords: template_report linux fedora Cc:

Description

What steps will reproduce the problem?

  1. Start using JOSM

What happens instead?

JOSM uses 2 CPU cores at 100% load (of a quad core CPU) only to move the map.
Heavy general GUI slowness

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

Revision: 8109
Is-Local-Build: true
Build-Date: 2015-03-03 19:34:02

Identification: JOSM/1.5 (8109 SVN it) Linux Fedora release 21 (Twenty One)
Memory Usage: 479 MB / 3566 MB (421 MB allocated, but free)
Java version: 1.8.0_40-debug, Oracle Corporation, OpenJDK 64-Bit Server VM

Plugins:
- FastDraw (30892)
- HouseNumberTaggingTool (30892)
- OpeningHoursEditor (30962)
- contourmerge (1012)
- download_along (30892)
- editgpx (30892)
- geochat (31056)
- jts (31002)
- log4j (30892)
- mirrored_download (30962)
- print (30892)
- reverter (30990)

Last errors/warnings:
- W: PluginException: File jar non valido '/home/user/.josm/plugins/geotools.jar.new'
- W: Fallita la scansione del file 'geotools.jar.new' per le informazioni dell'estensione. Tralascio.
- W: Fallita l'installazione dell'estensione '/home/user/.josm/plugins/geotools.jar' dal file di scaricamento temporaneo '/home/user/.josm/plugins/geotools.jar.new'. error in opening zip file

Fedora bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1209842

Attachments (0)

Change History (10)

comment:1 by skyper, 11 years ago

Owner: changed from team to germano
Status: newneedinfo
  • Does the problem also exist with the official .jar files ?
  • How big was your data ?
  • Which styles where active ?
  • Does the same problem exist using openjdk-7 ?
  • Did you try it without plugins by using the new command line option --skip-plugins or complete new .josm directory ?

in reply to:  1 ; comment:2 by stoecker, 11 years ago

Additional question: Which background imagery did you use?

You should remove '/home/user/.josm/plugins/geotools.jar.new' and reinstall the plugin. Something went wrong with the plugin installation.

in reply to:  2 comment:3 by germano, 11 years ago

Replying to skyper:

  • Does the problem also exist with the official .jar files ?

Yes

  • How big was your data ?

Very little, but it is not a matter of data, because JOSM is slow even if I don't load anything

  • Which styles where active ?

Styles?

  • Does the same problem exist using openjdk-7 ?

I can't try because on Fedora 21 there are only Java => 1.8 packages

  • Did you try it without plugins by using the new command line option --skip-plugins or complete new .josm directory ?

Yes I even tried erasing .josm dir

comment:4 by stoecker, 11 years ago

Hmm, How exactly is JOSM started? If it is started using a batch script, please post the commandline from the script. This sounds much like an issue with the graphics. Maybe OpenGL related.

Here is how the start from openSUSE looks like:

LIBXCB_ALLOW_SLOPPY_LOCK=1 java -Xms64M -Xmx1024M -XX:+UseParallelGC -XX:+UseAdaptiveSizePolicy -jar /usr/share/java/josm-tested.jar

comment:5 by Don-vip, 11 years ago

Keywords: linux fedora added

in reply to:  4 comment:6 by germano, 11 years ago

Replying to stoecker:

Hmm, How exactly is JOSM started? If it is started using a batch script, please post the commandline from the script. This sounds much like an issue with the graphics. Maybe OpenGL related.

Here is how the start from openSUSE looks like:

LIBXCB_ALLOW_SLOPPY_LOCK=1 java -Xms64M -Xmx1024M -XX:+UseParallelGC -XX:+UseAdaptiveSizePolicy -jar /usr/share/java/josm-tested.jar

$ cat /usr/bin/josm
#!/bin/sh
# Simple wrapper script used to start JOSM

# to prefer jre version and not java-devel version
_prefer_jre=1

# Source functions library
if [ -f /usr/share/java-utils/java-functions ] ; then

. /usr/share/java-utils/java-functions

else

echo "Can't find functions library, aborting"
exit 1

fi

# Configuration
MAIN_CLASS="JOSM"
BASE_JARS="josm metadata-extractor2-2 ant signpost-core apache-commons-codec svgsalamander gnu-getopt xmpcore apache-commons-compress"

# Set parameters
set_classpath $BASE_JARS

# Let's start
run "$@"

comment:7 by germano, 11 years ago

Instead when I started the official jar file, I did:
$ java -jar josm josm-snapshot-8109.jar

comment:8 by stoecker, 11 years ago

More questions:

  • What graphics card and which drivers do you have?
  • What Desktop do you use: KDE, GNOME, ...?
  • Have you another desktop (maybe one of the smaller ones) also installed? If yes, same situation there?
  • Does "-Dsun.java2d.opengl=false" as argument to java help? or "true"?

in reply to:  8 comment:9 by germano, 11 years ago

Replying to stoecker:

More questions:

  • What graphics card and which drivers do you have?

# lspci -k | grep -iA 3 vga
01:00.0 VGA compatible controller: NVIDIA Corporation GT200 [GeForce GTX 260] (rev a1)

Subsystem: ASUSTeK Computer Inc. Device 831c
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia

  • What Desktop do you use: KDE, GNOME, ...?

KDE 4.14.6

  • Have you another desktop (maybe one of the smaller ones) also installed?

No

  • Does "-Dsun.java2d.opengl=false" as argument to java help? or "true"?

both false and true opetion did not help

comment:10 by stoecker, 11 years ago

Resolution: irreproducible
Status: needinfoclosed

There is nothing obviously wrong. It may be the proprietary graphics driver or another component. You can only experiment to find the related component (i.e. does it happen only for JOSM or also other Java programs). Maybe try a live linux like Knoppix or Fedora Live also.

If you find the reason, please document it here for others.

Closing, as ATM we can't do anything.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain germano.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.