Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #38276 > unrolled thread

Any way to prevent this bug?

Started byEric Douglas <e.d.programmer@gmail.com>
First post2018-05-23 06:55 -0700
Last post2018-05-23 08:31 -0700
Articles 3 — 2 participants

Back to article view | Back to comp.lang.java.programmer


Contents

  Any way to prevent this bug? Eric Douglas <e.d.programmer@gmail.com> - 2018-05-23 06:55 -0700
    Re: Any way to prevent this bug? Eric Sosman <esosman@comcast-dot-net.invalid> - 2018-05-23 11:13 -0400
      Re: Any way to prevent this bug? Eric Douglas <e.d.programmer@gmail.com> - 2018-05-23 08:31 -0700

#38276 — Any way to prevent this bug?

FromEric Douglas <e.d.programmer@gmail.com>
Date2018-05-23 06:55 -0700
SubjectAny way to prevent this bug?
Message-ID<21965215-6c26-48fd-aef9-199e00ea9862@googlegroups.com>
I just got this message, didn't crash my application but wrote to my logs.
It appears to be this bug (https://bugs.openjdk.java.net/browse/JDK-8179665) but that claims it's fixed.
I'm running Java 8 update 161.
It doesn't say what in my code may have triggered it, just that it comes from EDT.

java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location
	at java.awt.Component.getLocationOnScreen_NoTreeLock(Unknown Source)
	at java.awt.Component.getLocationOnScreen(Unknown Source)
	at javax.swing.text.JTextComponent$InputMethodRequestsHandler.getTextLocation(Unknown Source)
	at sun.awt.im.InputMethodContext.getTextLocation(Unknown Source)
	at sun.awt.windows.WInputMethod$1.run(Unknown Source)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
	at java.awt.EventQueue.access$500(Unknown Source)
	at java.awt.EventQueue$3.run(Unknown Source)
	at java.awt.EventQueue$3.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.awt.EventQueue$4.run(Unknown Source)
	at java.awt.EventQueue$4.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

[toc] | [next] | [standalone]


#38283

FromEric Sosman <esosman@comcast-dot-net.invalid>
Date2018-05-23 11:13 -0400
Message-ID<pe40ev$8gm$1@dont-email.me>
In reply to#38276
On 5/23/2018 9:55 AM, Eric Douglas wrote:
> I just got this message, didn't crash my application but wrote to my logs.
> It appears to be this bug (https://bugs.openjdk.java.net/browse/JDK-8179665) but that claims it's fixed.
> I'm running Java 8 update 161.

     The bug page lists the Java versions to which the fix was
backported; 8-161 is not among them.  Either upgrade, or live
with the bug.

-- 
esosman@comcast-dot-net.invalid
Nine hundred seventy-three days to go.

[toc] | [prev] | [next] | [standalone]


#38286

FromEric Douglas <e.d.programmer@gmail.com>
Date2018-05-23 08:31 -0700
Message-ID<a42827e3-1715-4991-bb1f-9e88688fc92d@googlegroups.com>
In reply to#38283
On Wednesday, May 23, 2018 at 11:13:44 AM UTC-4, Eric Sosman wrote:
>      The bug page lists the Java versions to which the fix was
> backported; 8-161 is not among them.  Either upgrade, or live
> with the bug.

I see, so this was fixed recently then edited into the older versions.  I was thinking resolved and applied to update 131 should mean it's not an issue with later versions.  Apparently they fixed it in 162 as well but not 161.  These dual releases are challenging.  I guess it's time to install 171.

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.java.programmer


csiph-web