Opened 8 years ago

Closed 8 years ago

#11997 closed defect (othersoftware)

java.lang.IllegalArgumentException: Window must not be zero

Reported by: mikini Owned by: mikini
Priority: normal Milestone:
Component: Core Version: tested
Keywords: template_report javabug linux ubuntu Cc:


What steps will reproduce the problem?

I am afraid I haven't got steps to reproduce the symptom yet as it occurs periodically in different situations.

What is the expected result?

Further editing is possible.

What happens instead?

I have noticed two situations in which it occurred, the bug information below is from 2:

  1. When adding a new relation the exception occurred while trying to edit it to add a way. An exception dialog appeared with option to report or ignore. After opening the ticket reporter closing the dialog returned back to the editor which seemed still functional except the exception reoccuring repeatedly when trying to edit the relation. I was able to continue editing and upload with the exception of keyboard shortcuts being ignored. The bug report from this incident was never reported but it was positively the same "Window must not be zero" exception.
  1. When trying to add tags to a newly added way by pressing alt-a the same dialog appeared resulting in this bug report. In the same way I could continue editing but without keyboard shortcuts being available. This time the exception reoccurred a couple of times but after that I could continue tagging. It seemed like the window did not have proper focus as the menu bar didn't become highlighted as it should. Nevertheless pointer movements, mouse clicks and keyboard input in upload/tagging were received by the application. Suddenly though it froze and after letting it hang a while it reported excessive memory use (around 1.8GiB) when trying to close the window. At this point I made the following dump of the process:
    $ ps -p 26691 -v
    26691 ?        Sl    33:04  16338     2 4652361 2207468 28.4 java -jar /home/miki/Desktop/josm-tested.jar

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

Screenshot from incident 1: see attachement "Screenshot from 2015-10-19 01:59:03.png"
Screenshot from incident 2: see attachement "Screenshot from 2015-10-21 23:12:43.png"

$ lsb_release -a
LSB Version:	core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 14.10
Release:	14.10
Codename:	utopic
Repository Root:
Build-Date: 2015-09-28 01:32:03
Last Changed Author: simon04
Revision: 8800
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Relative URL: ^/trunk
Last Changed Date: 2015-09-27 22:11:06 +0200 (Sun, 27 Sep 2015)
Last Changed Rev: 8800

Identification: JOSM/1.5 (8800 en) Linux Ubuntu 14.10
Memory Usage: 900 MB / 1682 MB (478 MB allocated, but free)
Java version: 1.7.0_79, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-7-jre:amd64-7u79-2.5.5-0ubuntu0.14.10.2
Dataset consistency test: No problems found

- buildings_tools (31603)
- osmarender (31603)

Last errors/warnings:
- W: Could not connect to the OSM server. Please check your internet connection.. Cause:
- E:
- W: Could not connect to the OSM server. Please check your internet connection.. Cause:
- E: java.lang.IllegalArgumentException: Window must not be zero
- E: java.lang.IllegalArgumentException: Window must not be zero

java.lang.IllegalArgumentException: Window must not be zero
	at sun.awt.X11.WindowPropertyGetter.<init>(
	at sun.awt.X11.WindowPropertyGetter.<init>(
	at sun.awt.X11.XlibUtil.isToplevelWindow(
	at sun.awt.X11.XWindowPeer.setToplevelTransientFor(
	at sun.awt.X11.XWindowPeer.updateTransientFor(
	at sun.awt.X11.XWindowPeer.setModalBlocked(
	at sun.awt.X11.XDialogPeer.blockWindows(
	at java.awt.Dialog.blockWindows(
	at java.awt.Dialog.modalShow(
	at java.awt.Dialog.conditionalShow(
	at java.awt.Component.setVisible(
	at java.awt.Window.setVisible(
	at java.awt.Dialog.setVisible(
	at org.openstreetmap.josm.gui.ExtendedDialog.setVisible(
	at org.openstreetmap.josm.gui.ExtendedDialog.showDialog(
	at java.awt.event.InvocationEvent.dispatch(
	at java.awt.EventQueue.dispatchEventImpl(
	at java.awt.EventQueue.access$300(
	at java.awt.EventQueue$
	at java.awt.EventQueue$
	at Method)
	at java.awt.EventQueue.dispatchEvent(
	at java.awt.EventDispatchThread.pumpOneEventForFilters(
	at java.awt.EventDispatchThread.pumpEventsForFilter(
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(
	at java.awt.EventDispatchThread.pumpEvents(
	at java.awt.EventDispatchThread.pumpEvents(

Attachments (2)

Screenshot from 2015-10-19 01:59:03.png (2.0 MB) - added by mikini 8 years ago.
Incident 1 screenshot
Screenshot from 2015-10-21 23:12:43.png (2.6 MB) - added by mikini 8 years ago.
Incident 2 screenshot

Change History (8)

Changed 8 years ago by mikini

Incident 1 screenshot

Changed 8 years ago by mikini

Incident 2 screenshot

comment:1 Changed 8 years ago by Don-vip

Component: Core bugreportCore

comment:2 Changed 8 years ago by Don-vip

Owner: changed from team to mikini
Status: newneedinfo

I see you're using a dual-screen setup on Ubuntu. This configuration is known to provoke some geometry bugs, see #9699.

It can lead to bugs such as javabug:8020443, which is fixed in Java 7u85 and 8u60.

My best advise is to first update to Ubuntu 15.10 (Wily) ==> you will get 7u85.

Tell us then if you still face the error.

comment:3 Changed 8 years ago by Don-vip

Keywords: javabug linux ubuntu added

comment:4 Changed 8 years ago by Don-vip

Have you been able to upgrade to latest Ubuntu?

comment:5 Changed 8 years ago by mikini

Thanks for info and keeping track on this. That particular machine is tied to 14.10 at the moment because of dependencies in other development work. I'm on track to upgrade when possible and will let you know how it turns out.
Can use JOSM if careful, but seems like my normally used triple monitor setup is triggering it more than my dual one. Let me know if there's any specific or special circumstances I should test out.

comment:6 Changed 8 years ago by Don-vip

Resolution: othersoftware
Status: needinfoclosed

OK. I think the bug is identified, I just wanted to be sure. I'm closing the ticket for now, please reopen it if you still get the error with the latest version of Java.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain mikini.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.