Opened 5 years ago
Last modified 4 years ago
#19585 closed defect
IAE: Width and height must be >= 0 — at Version 51
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | critical | Milestone: | 21.03 |
| Component: | Core | Version: | |
| Keywords: | template_report IAE linux java11 tooltip metal javabug | Cc: | simon04, mnalis, dx125, OSM_RogerWilco, SoCal, Maplove, SpillerC, Strubbl, Win32netsky, A_Pirard, icke68746 |
Description (last modified by )
What steps will reproduce the problem?
I do not know or simply using JOSM. Bug Report Dialog rises on different actions like simply clicks in Mapview or closing a relation editor.
What is the expected result?
No Bug Report Dialogs
What happens instead?
Bug Report Dialogs
Please provide any additional information below. Attach a screenshot if possible.
I just updated java from 11.0.7+ to 11.0.8+.
#11123 looks similar. So I suspect this to be a java bug but maybe a workaround is possible.
I reported this to my JRE package maintainers, see Debian Bug #967049.
As of 2020-11-11 all duplicate reports are with:
- MetalLookAndFeel
- Linux Suse/Ubuntu/Debian/Flathub
- openjdk-jre 11.0.8 / 11.0.9
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2020-07-26 09:33:11 +0200 (Sun, 26 Jul 2020) Revision:16809 Build-Date:2020-07-27 01:30:49 URL:https://josm.openstreetmap.de/svn/trunk Identification: JOSM/1.5 (16809 en) Linux Debian GNU/Linux 10 (buster) Java version: 11.0.8+10-post-Debian-1deb10u1, Debian, OpenJDK 64-Bit Server VM Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel Last errors/warnings: - E: Handled by bug report queue: java.lang.IllegalArgumentException: Width and height must be >= 0 - E: Handled by bug report queue: java.lang.IllegalArgumentException: Width and height must be >= 0 === REPORTED CRASH DATA === BugReportExceptionHandler#handleException: No data collected. Warning issued by: BugReportExceptionHandler#handleException === STACK TRACE === Thread: AWT-EventQueue-0 (18) of main java.lang.IllegalArgumentException: Width and height must be >= 0 at java.desktop/javax.swing.plaf.basic.BasicHTML.getHTMLBaseline(BasicHTML.java:91) at java.desktop/javax.swing.plaf.metal.MetalToolTipUI.paint(MetalToolTipUI.java:126) at java.desktop/javax.swing.plaf.ComponentUI.update(ComponentUI.java:161) at java.desktop/javax.swing.JComponent.paintComponent(JComponent.java:797) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1074) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1083) at java.desktop/javax.swing.JLayeredPane.paint(JLayeredPane.java:590) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:907) at java.desktop/javax.swing.JComponent.paintToOffscreen(JComponent.java:5262) at java.desktop/javax.swing.RepaintManager$PaintManager.paintDoubleBufferedImpl(RepaintManager.java:1643) at java.desktop/javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1618) at java.desktop/javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1556) at java.desktop/javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:262) at java.desktop/javax.swing.RepaintManager.paint(RepaintManager.java:1323) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1060) at java.desktop/java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback.java:39) at java.desktop/sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:78) at java.desktop/sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:115) at java.desktop/java.awt.Container.paint(Container.java:2002) at java.desktop/java.awt.Window.paint(Window.java:3940) at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:876) at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:848) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:848) at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:823) at java.desktop/javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:772) at java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1890) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Change History (51)
comment:1 by , 5 years ago
follow-up: 8 comment:2 by , 5 years ago
I faced this exception only after the first startup with the new java version. Yesterday, I did not face it, though, I was not editing much.
comment:6 by , 5 years ago
Replying to Klumbumbus:
all reports are with Metal Look And Feel.
Yeah, and so far with debian-based Linux with openjdk 11.0.8+10-post
comment:8 by , 5 years ago
Replying to skyper:
I faced this exception only after the first startup with the new java version. Yesterday, I did not face it, though, I was not editing much.
Does not happen that often but I just got it, again.
Let's see what package maintainers say about it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967049
comment:11 by , 5 years ago
| Priority: | normal → major |
|---|
comment:12 by , 5 years ago
| Description: | modified (diff) |
|---|---|
| Keywords: | linux java11 added |
Maybe, an Ubuntu user is willed to report this against the Ubuntu package on launchpad.
comment:13 by , 5 years ago
| Description: | modified (diff) |
|---|
comment:14 by , 5 years ago
| Description: | modified (diff) |
|---|
follow-up: 23 comment:22 by , 5 years ago
| Cc: | added |
|---|
follow-up: 35 comment:23 by , 5 years ago
Replying to Klumbumbus:
I have the slight feeling that this bug was triggered by the rework in #19381, because I think I read "upload" in several of the duplicate reports and #11123 was about resizing windows too.
No, I get it with all kinds of dialogs like relation manager, validator panel, history viewer etc.. Have to watch out, if it only happens with separate dialogs and undocked panels.
Have a look at Don-vip's on #11123 comment:10:
OK reproduced on Ubuntu, and on Windows too by enabling the Metal L&F. It's a bug of Java (javabug:6719550) itself that can happen even if our tooltip has positive dimensions. Netbeans guys already encountered the bug and silently ignored the exception, I'll do the same.
I am not sure if is tight to metal look-and-feel but I am pretty sure that something changed in openjdk-11-jre with the last security update, as I remember the josm version did not change that day and I only faced this exception after the java update.
Probably the easiest solution on our side is to silently ignore this warning.
comment:28 by , 5 years ago
| Description: | modified (diff) |
|---|
comment:29 by , 5 years ago
| Description: | modified (diff) |
|---|---|
| Keywords: | tooltip added |
comment:33 by , 5 years ago
| Description: | modified (diff) |
|---|
follow-up: 37 comment:35 by , 5 years ago
Replying to skyper:
Probably the easiest solution on our side is to silently ignore this warning.
Not easy at all. The error happens in the EDT, not in a JOSM thread. The question is really why so many people are using Metal?
comment:36 by , 5 years ago
| Description: | modified (diff) |
|---|---|
| Keywords: | metal added |
| Priority: | major → critical |
comment:37 by , 5 years ago
Replying to Don-vip:
The question is really why so many people are using Metal?
I did use it together with Gnome, as the Gtk-Theme has bigger elements and therefore less content is displayed.
Is the Look-And-Feel set properly on the first startup or does every user have to set it once, manually?
comment:38 by , 5 years ago
I never choose a GTK theme (as far as I remember) but my JOSM on Ubuntu uses Metal. So it looks like a default value.
comment:45 by , 5 years ago
In #20011 there is also a hint about the problematic JOSM code in the stacktrace:
org.openstreetmap.josm.gui.ExtendedDialog.setVisible(ExtendedDialog.java:459)
follow-up: 50 comment:48 by , 5 years ago
for the record, I've had this problem (in dupe #20060) and I'm not using any DE, but just icewm on Debian Buster (with "icedesert" theme)
comment:49 by , 5 years ago
| Cc: | added |
|---|
comment:50 by , 5 years ago
Replying to mnalis:
for the record, I've had this problem (in dupe #20060) and I'm not using any DE, but just icewm on Debian Buster (with "icedesert" theme)
Sorry for not adding you to "cc".
This problem does not depend on X or WM but on the java theme (Metal) used and openjdk-11-jre version 11.0.8+. You may want to comment on the debian bug 967049.
comment:51 by , 5 years ago
| Description: | modified (diff) |
|---|
Ticket #19593 has been marked as a duplicate of this ticket.