Opened 8 years ago
Closed 8 years ago
#12145 closed defect (duplicate)
freeze/crash when sending URL to browser
Reported by: | malenki | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | java8 linux | Cc: |
Description
How to reproduce:
Pick an object existing in the OSM DB already.
Press ctrl-shift-i or ctrl-shift-h.
More often (guesstimation 75%) then not JOSM just freezes – one cannot do a thing except kill the java process. Kill -14 is sufficient.
Seldom it happens that JOSM crashes. I remember the last line of the CLI output saying something about "resource on X0:0 not available". Since a crash is hard to reproduce I am sorry I cannot be more verbose.
Tested in r9066, experienced it also earlier.
Tested with blank ~/.josm
openjdk version "1.8.0_66-internal"
OpenJDK Runtime Environment (build 1.8.0_66-internal-b01)
OpenJDK 64-Bit Server VM (build 25.66-b01, mixed
The problem does not occur with
java version "1.7.0_91"
OpenJDK Runtime Environment (IcedTea 2.6.3) (7u91-2.6.3-1~deb8u1)
OpenJDK 64-Bit Server VM (build 24.91-b01, mixed mode)
I use an up-to-date LMDE2 4.2.0-1-amd64 #1 SMP Debian 4.2.5-1 (2015-10-27) x86_64 GNU/Linux. WM is Marco.
Attachments (0)
Change History (13)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Keywords: | java8 added |
---|
comment:3 by , 8 years ago
$ josm-latest --debug
Open Relation Page with ctrl-shift-i
INFO: Öffne URL: https://www.openstreetmap.org/relation/3209500
INFO: GET https://api.openstreetmap.org/api/0.6/user/details (Anzahl der ungelesenen Nachrichten abrufen) -> 200 (390 B)
DEBUG: RESPONSE: {Keep-Alive=[timeout=5, max=100], Status=[200 OK], null=[HTTP/1.1 200 OK], Server=[Apache/2.4.7 (Ubuntu)], X-Request-Id=[VoBbn8AAQEAACVCUcsAAACO], X-Content-Type-Options=[nosniff], X-Runtime=[0.045829], Connection=[Keep-Alive], Date=[Fri, 08 Jan 2016 09:29:18 GMT], X-Frame-Options=[SAMEORIGIN], Cache-Control=[max-age=0, private, must-revalidate], ETag=[W/"814b1e2e7fa8d11c174faafbfc91c59a-gzip"], Content-Encoding=[gzip], Set-Cookie=[_osm_session=acaa208879ccd23e7a11c8650eeeea40; path=/; HttpOnly], Vary=[Origin,Accept-Encoding], Content-Length=[390], X-XSS-Protection=[1; mode=block], Content-Type=[text/xml; charset=utf-8], X-Powered-By=[Phusion Passenger 5.0.23]}
comment:4 by , 8 years ago
And some times (in about 10% of the cases) it works. It you are in this case, you can open all URLs without futher problems.
The fastest way to test is clicking on the "development" link on the start page.
follow-up: 8 comment:6 by , 8 years ago
can you please try again after disabling Gnome ATK Wrapper? (see #12022)
comment:7 by , 8 years ago
Keywords: | linux added |
---|
comment:8 by , 8 years ago
Replying to Don-vip:
can you please try again after disabling Gnome ATK Wrapper? (see #12022)
I went back to the more up-to-date Siduction distribution which provides a more recent java:
openjdk version "1.8.0_72-internal"
OpenJDK Runtime Environment (build 1.8.0_72-internal-b05)
OpenJDK 64-Bit Server VM (build 25.72-b05, mixed mode)
Now I cannot reproduce the error I describe in the ticket.
follow-up: 11 comment:9 by , 8 years ago
It looks like the problem is the assistive_technologies=org.GNOME.Accessibility.AtkWrapper
in /etc/java-8-openjdk/accessibility.properties
. As far as I could see only a few operating systems use this feature. Even openjdk for Windows has no assistive technologies defined. And for Ubuntu only openjdk8 has this feature activated.
If you use an other Linux distribution, accessibility.properties
may contain no active assistive_technologies
entry.
@Don-vip: Is there a possibility to overrule the settings in /etc/java-8-openjdk/accessibility.properties
on the command line? I think it would be better if we could change the start script instead of telling each Ubuntu user to modify his properties file manually.
comment:10 by , 8 years ago
Hint: I was running Linux Mint Debian Edition (LMDE) as I stumbled of this issue.
comment:11 by , 8 years ago
Replying to mdk:
@Don-vip: Is there a possibility to overrule the settings in
/etc/java-8-openjdk/accessibility.properties
on the command line? I think it would be better if we could change the start script instead of telling each Ubuntu user to modify his properties file manually.
I don't know, I'll give it a look.
comment:13 by , 8 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Same here, Ubuntu 15.10 with openjdk 1.8 -> hangs on Shift-Ctrl-H
with openjdk 1.7 it works fine
I could only get rid of the hanging java process with kill -9 though