JDK-8160563 : jvm crash at javafx com.sun.webkit.WebPage.twkPrePaint (GFlag + Heap verification)
  • Type: Bug
  • Component: javafx
  • Sub-Component: web
  • Affected Version: 8u112,9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_7
  • CPU: x86
  • Submitted: 2016-06-29
  • Updated: 2017-09-07
  • Resolved: 2016-07-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9
8u112Fixed 9 masterFixed
Description
jvm crash at javafx com.sun.webkit.WebPage.twkPrePaint at http://www.usatoday.com site

Steps to reproduce : 
Pre-condition : enable Heap verification for JAVA_HOME\bin\java.exe 
ref : https://msdn.microsoft.com/en-us/library/windows/hardware/ff549561(v=vs.85).aspx 

1. Use hello.HelloWebView (from toys) and load http://www.usatoday.com 
2. wait for site to render (~60 seconds) 
3. Application will crash
Comments
Changeset: 05818f57d96a Author: ghb Date: 2016-07-05 21:47 +0530 URL: http://hg.openjdk.java.net/openjfx/9-dev/rt/rev/05818f57d96a
05-07-2016
Looks good to me.
05-07-2016
lgtm +1 You need to create a shadow bug with minimal information to push the changes.
05-07-2016
Webrev : http://cr.openjdk.java.net/~ghb/8160563/webrev.00/ RC : strlen() for Non null terminated was leading to crash, while running Java using Gflag (Heap validation). Fix : Re-use an already created String object from Textrun instead of creating a new object. Test: Crash only occurs on Windows with Gflag Heap validation enabled.
05-07-2016
Reproduced with Java(TM) SE Runtime Environment (build 1.8.0_112-ea-b01) 1. Is this crash always reproducible ? Yes. I see it always with http://www.usatoday.com/ 2. webviewbrowser.jar is used for "elapsed time: 2924 seconds (0d 0h 48m 44s)". Just a first of crash dumps was attached. On my last appempt app crashed in about 20 seconds...
01-07-2016
Please provide the additional info to debug further
30-06-2016
[~mkhramov] I wasn't able to reproduce the crash using "8u112 b 01 (1.8.0_112 b1)" nor with our latest 8u-dev / 9-dev (openjfx build + 8u112 b01). 1. Is this crash always reproducible ? 2. webviewbrowser.jar is used for "elapsed time: 2924 seconds (0d 0h 48m 44s)". I assume this application is launched and must have been loaded some other webpage before this crash occurred. If you could remember what are the webpage you used for testing (Before the crash occurred) will help us to re-produce the crash and analyse further. I have see similar defects with "RULE sites/somewebpage.com" any any" . Where are these list is been selected ?. Are you using alexa ranking ? or do we have some pre set of web sites used for testing during our PSU release?
30-06-2016
This is likely some sort of OOM error.
29-06-2016
RULE "sites/usatoday.com" any any
29-06-2016
Tested product: Java(TM) SE Runtime Environment 1.8.0_112 b1 (1.8.0_112-ea-langtools-nightly-h9032-20160609-b01) 8u102 build 14 was works ok.
29-06-2016