Hexagon Geospatial
MENU

GeoMedia Smart Client

GeoMedia Smart Client community discussion board is where you can create, contribute and share information and knowledge in regards to configuring as well as working with GeoMedia Smart Client. Find your answers, share your knowledge and help build a strong GeoMedia Smart Client community.
Showing results for 
Search instead for 
Do you mean 
Reply
Moderator
Posts: 247
Registered: ‎02-08-2016

WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

[ Edited ]

Hello All:

 

 

A new bug report has been logged with Oracle in regards to the most recent java update, Java 8u161 and Java 8u162.

It apears there is an issue JavaFx/Swing component which will cause GMSC to crash when the Java Webbrowser is used and focus is changed to another application and then back to the Java Webbrowser. 

 

If you are experiencing this issue please use a previous version of Java until a fix is available.

 

Thank You,

Marc

 

Occasional Contributor
Posts: 11
Registered: ‎03-31-2016

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

Marc,

 

do you have more details about this issue like an Oracle Bug number, expected fix date, etc.?

 

Thanks

Frank

Moderator
Posts: 247
Registered: ‎02-08-2016

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

Hello Frank.

 

The bug oracle bug number JDK-8196011.

Unfortunately the fix date will be determined by Oracle.

 

Thank You,

Marc

Contributor
Posts: 23
Registered: ‎01-31-2018

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

[ Edited ]

About JDK-8196011:
Today, the issue seems to have changed from being adressed in JDK 10 to JDK 11.
JDK 11 is scheduled to be released in Sep 2018 (http://www.oracle.com/technetwork/java/eol-135779.html).
Do we really have to ask our users to run GMSC with JRE 8u151/152 that long? Some of them HAVE already upgraded to 8u161 before the bug in JavaFX was officially publicated, and are now facing the problem not to find the installer for JRE 8u151 on the net.

Besides: IMHO the technical discussion in JDK-8196011 does not pick up the origin of the problem: It's not about wikipedia.org having an anchor with lang="roa-x-eml" and some queer unicode chars in the innerText. It's about memory access violations caused by the com.sun.webkit.WebPage class.

We do not want to display the wikipedia start page using the GMSC workflow engine.
We want our users to be able to use GMSC forms without getting the whole process crashed (if it goes down to application-window-changes, just consider selecting a file for upload in a select-file-dialog may crash, because it moves the focus from WebView to an OS-specific dialog).

Speaking in terms of LogLevels: it's not even CRITICAL, it's somehow PANIC!

Technical Evangelist
Posts: 148
Registered: ‎10-20-2015

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

Hi ElLuce,

the change from JDK10 to JDK11 is a typcial behaviour of Oracle that we have also seen at other reported issues. They often target/plan the bug fix to a version which is still in development. JDK 10 will be released in March 2018 and reached the "Initial Release Candidate" phase (see JDK 10 Schedule) . If the bug is resolved, then Oracle creates a backport if it is possible/necessary.

 

 

Besides: IMHO the technical discussion in JDK-8196011 does not pick up the origin of the problem: It's not about wikipedia.org having an anchor with lang="roa-x-eml" and some queer unicode chars in the innerText. It's about memory access violations caused by the com.sun.webkit.WebPage class.

 

We informed Oracle about two bugs at the https://bugs.java.com/view_bug.do?bug_id=JDK-8196011.

  1. The crash of the WebKit itself which happens e.g. in case of opening http://www.wikipedia.org
  2. and the crash because of the focus change which is listed at the comments of JDK-8196011. The date of the comment is "2018-01-24"
    Additional Information from submitter:
    ----------------------------------------------------------------
    Hi,
    I found now a sequence which reproduces the focus-change issue what we have at our application by using the provided JFXTest sample.
    You can change the url to "http://www.google.com" and will see that also some minimalistic pages are affected.

    Steps to reproduce:
    (1) Change the URL at line 31 to "http://www.google.com"
    2. Execute the JFXTest program
    3. Click on the "Open a JFrame button"
    4. Move the window so that you can open a second WebBrowser by clicking on "Open a JFrame button"
    5. Change the focus to another application e.g. Outlook, Chrome etc...
    6. Go back to the second WebBrowser frame and: -> click on a link like "Playstore" -> or sometimes it also work if you wait a few seconds.. 

We started the bug report with the first issue because of the fact that the second one wasn't explicit reproduceable.

 

Oracle stated on 2018-01-25 that they can reproduce the crash by using our second scenario.

When ran reproducible test case - JFXTest.java, i am able to reproduce crash using 8u161-b12 & 8u162-b03 on windows 64-bit. PFA error report files - hs_err_pid19872.log & hs_err_pid11292.log

 

Furthermore we and one of our customers tested the 32-bit & 64-bit version of the next JRE 8u172 which is available at: http://jdk.java.net/8/. We can confirm that the crash of the second procedure (focus change) and in combination with GeoMedia Smart Client 2016 doesn't happen any more.

 

 

 

In addition we tested the JRE versions of the upcoming GeoMedia Smart Client 2018 focus-issue and can confirm that the focus-crash doesn't happen at JRE 9.0.4, JRE-10-ea+42.

 

If you have any further questions, do not hesitate to contact me at this thread. I will answer them as soon as possible.

 

Thanks in advance!

Best Regards,

Steve Hruda

 

Technical Evangelist
Posts: 148
Registered: ‎10-20-2015

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

Hi,

ORACLE changed the status of JDK-8196011 to resolved. The fix will be included at 10.0.2 and 8u182. We will verify that as soon as a Early Access Version of these JRE's is available.

 

At the moment the offical JDK 8 Update Release page doesn't include a timeline for 8u182 but at https://bugs.openjdk.java.net is July 2018 mentioned.

 

https://bugs.openjdk.java.net/projects/JDK?selectedItem=com.atlassian.jira.jira-projects-plugin:rele...

 

I would like to point out again, that customers tested the 32-bit & 64-bit version of the next JRE 8u172 which is available at: http://jdk.java.net/8/. We can confirm that the crash of the second procedure (focus change) and in combination with GeoMedia Smart Client 2016 doesn't happen any more.

 

Best Regards,

Steve

Technical Evangelist
Posts: 148
Registered: ‎10-20-2015

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

Hi all,

we tested the offical release of Java 8u171 and 8u172.

 

As I already mentioned at my last post, Oracle defined the issue fixed at 8u181 but we can't observe the focus-crash at 8u171 & 8u172.

At the moment are no Early Access builds for 8u81 available at http://jdk.java.net/8/. 

 

Can you confirm that 8u171 and 8u172 improve the stability?

 

Best Regards,

Steve

Contributor
Posts: 23
Registered: ‎01-31-2018

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

Hi Steve,

 

The bug still exists in Java 8u171 (x86 and amd64) on at least MS Win 10 systems. The Java processes GMSC 2016 runs in may still be terminated because of a memory access violation when changing focus from the workflow window to another application and back again. Or: Simply have a workflow form including a FormFile, select a local file in the OpenFileDialog and confirm the selection by clicking the OK-Button.

 

However, we could not reproduce the crashes using Java 8u172 (again both archs, x86 and amd64). It seems, the fix has made its way into the feature release, although JDK-8196011 is not mentioned in the list of bug fixes included in 8u172 (JDK 8u172 Bug Fixes).

Technical Evangelist
Posts: 148
Registered: ‎10-20-2015

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

[ Edited ]

Hi ElLuce,

Thanks for your feedback! So in the end 8u171 looks more stable, but accoriding to your findings (FormFile) it is not stable enough for production use.

 

Which brings me to the conclusion that a update to 8u172 is recommended!

 

 

Best Regards,

Steve

 

 

 

Contributor
Posts: 23
Registered: ‎01-31-2018

Re: WARNING - Java 8u161 and Java 8u162 may crash GeoMedia Smart client

A brief update:

 

I also recommend using GMSC 2016 with Java 8u172, but have to admit, the mentioned Java version is not the definite mean for the reported bugs: Some of our power-users (they are "flying" through workflows and map reloads in light velocity) are facing crashes even with Java 8u172, but VERY OCCASIONALLY.

By inspecting the client log files I can say, the reason for this is again the calculation of the position of UI elements in the JFX browser (twkGetTextLocation and so on). But - once again - very occasionally and not reproducibly (at a rate comparable to the crashes under Java 8u151).

 

I really hope, Oracle will have this ultimately fixed with Java 8u181.

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.