date:20160411

Re: RFR: JDK-8075550 - Error "JavaFX runtime not found" in nashorn when load predefines scripts to import JavaFX packages

2016-04-11 Thread Michael Haupt

Hi Jim,

lower-case thumbs up!

Best,

Michael

> Am 08.04.2016 um 19:05 schrieb Jim Laskey (Oracle) :
> 
> The code was reworked to use jrtfs: instead of reading from javafx.jar.
> 
> http://cr.openjdk.java.net/~jlaskey/8075550/webrev/index.html
> https://bugs.openjdk.java.net/browse/JDK-8075550
> 
> 
> 

-- 

 
Dr. Michael Haupt | Principal Member of Technical Staff
Phone: +49 331 200 7277 | Fax: +49 331 200 7561
Oracle Java Platform Group | LangTools Team | Nashorn
Oracle Deutschland B.V. & Co. KG | Schiffbauergasse 14 | 14467 Potsdam, Germany

ORACLE Deutschland B.V. & Co. KG | Hauptverwaltung: Riesstraße 25, D-80992 
München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V. | Hertogswetering 163/167, 
3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Nederland, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
  Oracle is committed to developing 
practices and products that help protect the environment

[9] Review request for 8150181: javafx print jobs take 60 times longer than javax.print

2016-04-11 Thread mikhail cherkasov


Hi all,

Could you please review the fix for:
https://bugs.openjdk.java.net/browse/JDK-8150181
webrev:
http://cr.openjdk.java.net/~mcherkas/8150181/webrev.02/

Javafx print is slow because after sending node for printing
we wait 1 sec before checking that page was done,
see implPrintPage method:
   while (!pageDone) {
synchronized (monitor) {
try {
monitor.wait(1000);
} catch (InterruptedException e) {
}
}
}

so if you need to print 100 pages to pdf you will have to wait
for 100 seconds while with  javax.print it happens almost instantly.
I added "notify" when page is printed, so now we start a new printing 
without waiting.


Thanks,
Mikhail.

Re: RFR: JDK-8075550 - Error "JavaFX runtime not found" in nashorn when load predefines scripts to import JavaFX packages

2016-04-11 Thread Jim Laskey (Oracle)

Thank you.

> On Apr 11, 2016, at 9:52 AM, Sundararajan Athijegannathan 
>  wrote:
> 
> +1
> 
> On 4/11/2016 6:13 PM, Jim Laskey (Oracle) wrote:
>> Any one else.
>> 
>>> On Apr 11, 2016, at 9:13 AM, Michael Haupt  wrote:
>>> 
>>> Hi Jim,
>>> 
>>> lower-case thumbs up!
>>> 
>>> Best,
>>> 
>>> Michael
>>> 
 Am 08.04.2016 um 19:05 schrieb Jim Laskey (Oracle) 
 >:
 
 The code was reworked to use jrtfs: instead of reading from javafx.jar.
 
 http://cr.openjdk.java.net/~jlaskey/8075550/webrev/index.html 
 
 https://bugs.openjdk.java.net/browse/JDK-8075550
 
 
 
>>> -- 
>>> 
>>> 
>>> Dr. Michael Haupt | Principal Member of Technical Staff
>>> Phone: +49 331 200 7277 | Fax: +49 331 200 7561
>>> Oracle Java Platform Group | LangTools Team | Nashorn
>>> Oracle Deutschland B.V. & Co. KG | Schiffbauergasse 14 | 14467 Potsdam, 
>>> Germany
>>> 
>>> ORACLE Deutschland B.V. & Co. KG | Hauptverwaltung: Riesstraße 25, D-80992 
>>> München
>>> Registergericht: Amtsgericht München, HRA 95603
>>> 
>>> Komplementärin: ORACLE Deutschland Verwaltung B.V. | Hertogswetering 
>>> 163/167, 3543 AS Utrecht, Niederlande
>>> Handelsregister der Handelskammer Midden-Nederland, Nr. 30143697
>>> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>>>   Oracle is committed to developing 
>>> practices and products that help protect the environment
>>> 
>

Re: RFR: JDK-8075550 - Error "JavaFX runtime not found" in nashorn when load predefines scripts to import JavaFX packages

2016-04-11 Thread Sundararajan Athijegannathan

+1

On 4/11/2016 6:13 PM, Jim Laskey (Oracle) wrote:
> Any one else.
>
>> On Apr 11, 2016, at 9:13 AM, Michael Haupt  wrote:
>>
>> Hi Jim,
>>
>> lower-case thumbs up!
>>
>> Best,
>>
>> Michael
>>
>>> Am 08.04.2016 um 19:05 schrieb Jim Laskey (Oracle) >> >:
>>>
>>> The code was reworked to use jrtfs: instead of reading from javafx.jar.
>>>
>>> http://cr.openjdk.java.net/~jlaskey/8075550/webrev/index.html 
>>> 
>>> https://bugs.openjdk.java.net/browse/JDK-8075550
>>>
>>>
>>>
>> -- 
>>
>>  
>> Dr. Michael Haupt | Principal Member of Technical Staff
>> Phone: +49 331 200 7277 | Fax: +49 331 200 7561
>> Oracle Java Platform Group | LangTools Team | Nashorn
>> Oracle Deutschland B.V. & Co. KG | Schiffbauergasse 14 | 14467 Potsdam, 
>> Germany
>>
>> ORACLE Deutschland B.V. & Co. KG | Hauptverwaltung: Riesstraße 25, D-80992 
>> München
>> Registergericht: Amtsgericht München, HRA 95603
>>
>> Komplementärin: ORACLE Deutschland Verwaltung B.V. | Hertogswetering 
>> 163/167, 3543 AS Utrecht, Niederlande
>> Handelsregister der Handelskammer Midden-Nederland, Nr. 30143697
>> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>>    Oracle is committed to developing 
>> practices and products that help protect the environment
>>

status behind JDK-8149738

2016-04-11 Thread Matthieu BROUILLARD

Hi all,

In our application that integrates some webapps we are facing quite the
same error than the one reported at
https://bugs.openjdk.java.net/browse/JDK-8149738.
The issue above has been marked with 'bugdb_22696741' ; does it mean it is
referenced with more details elsewhere? Is there a known workaround?

In our use case, when navigating in the webview into some GWT based
application using 8u74-i586 (or 8u60-i586) we always crash the JVM and
using 8u74 (64 bits) everything works.
Doing additional tests revealed that 8u45-b51-i586 is working ; but
unfortunately we have already moved on to more recent JDKs for our entire
application.

Sadly I do not have a simple reproduction app to provide.
We also enable some prism debug settings without seeing anything relevant
in the logs ; activating the software pipeline didn't changed anything
neither.

Are there specific debug params for the webview, webkit & jfxwebkit.dll ?

The crash report looks the same than in the above issue:

# # # # # # # # # # # # # # # # #

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x5456b7c9, pid=5836,
tid=6260
#
# JRE version: Java(TM) SE Runtime Environment (8.0_74-b02) (build
1.8.0_74-b02)
# Java VM: Java HotSpot(TM) Client VM (25.74-b02 mixed mode windows-x86 )
# Problematic frame:
# C  [jfxwebkit.dll+0x8eb7c9]
...
#

---  T H R E A D  ---

Current thread (0x0563d000):  JavaThread "JavaFX Application Thread"
[_thread_in_native, id=6260, stack(0x05c7,0x05cc)]

siginfo: ExceptionCode=0xc005, reading address 0x002e0060

Registers:
EAX=0x002e0030, EBX=0x0011, ECX=0x0d457870, EDX=0x
ESP=0x05cbd578, EBP=0x, ESI=0x0d457870, EDI=0x0bae3030
EIP=0x5456b7c9, EFLAGS=0x00210246

Top of Stack: (sp=0x05cbd578)
0x05cbd578:   0d202f60 54580e41 0001 0001
...
0x05cbd5e8:   54a51a88  54510e95 0d2f89a0

Instructions: (pc=0x5456b7c9)
0x5456b7a9:   24 0c 01 75 35 8b 4e 14 8b c1 c1 e8 09 a8 01 75
...
0x5456b7d9:   06 74 07 8b ce e8 4d de ff ff 5e c2 08 00 cc cc


Register to memory mapping:

EAX=0x002e0030 is an unknown value
EBX=0x0011 is an unknown value
ECX=0x0d457870 is an unknown value
EDX=0x is an unknown value
ESP=0x05cbd578 is pointing into the stack for thread: 0x0563d000
EBP=0x is an unknown value
ESI=0x0d457870 is an unknown value
EDI=0x0bae3030 is an unknown value


Stack: [0x05c7,0x05cc],  sp=0x05cbd578,  free space=309k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
C  [jfxwebkit.dll+0x8eb7c9]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.sun.webkit.WebPage.twkProcessMouseEvent(JIIIZF)Z+0
j
 
com.sun.webkit.WebPage.dispatchMouseEvent(Lcom/sun/webkit/event/WCMouseEvent;)Z+141
j
 
javafx.scene.web.WebView.processMouseEvent(Ljavafx/scene/input/MouseEvent;)V+175
j
 
javafx.scene.web.WebView.lambda$registerEventHandlers$32(Ljavafx/scene/input/MouseEvent;)V+2
j  javafx.scene.web.WebView$$Lambda$87.handle(Ljavafx/event/Event;)V+8
j
 
com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(Ljavafx/event/Event;)V+5
j
 
com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(Ljavafx/event/Event;)V+28
j
 
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/EventType;Ljavafx/event/Event;)Ljavafx/event/Event;+29
j
 
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+8
j
 
com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+11
j
 
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+29
j
 
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
 
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17
j
 
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
 
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17
j
 
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
 
com.sun.javafx.event.EventUtil.fireEventImpl(Ljavafx/event/EventDispatchChain;Ljavafx/event/EventTarget;Ljavafx/event/Event;)Ljavafx/event/Event;+10
j
 
com.sun.javafx.event.EventUtil.fireEvent(Ljavafx/event/EventTarget;Ljavafx/event/Event;)Ljavafx/event/Event;+46
j
 
javafx.event.Event.fireEvent(Ljavafx/event/EventTarget;Ljavafx/event/Event;)V+30
j
 javafx.scene.Scene$MouseHandler.process(Ljavafx/scene/input/MouseEvent;Z)V+491
j
 
javafx.scene.Scene$MouseHandler.access$1500(Ljavafx/scene/Scene$MouseHandler;Ljavafx/scene/input/MouseEvent;Z)V+3
j

Re: status behind JDK-8149738

2016-04-11 Thread Kevin Rushforth

Without a native stack trace it will be hard to say whether this is the 
same bug or not.


Several fixes for other crashes (not specifically JDK-8149738) have 
recently gone into 8-dev for 8u102. An early access build of 8u102-b01 
with some of these fixes is available here:


https://jdk8.java.net/download.html

8u102-b02 will have additional WebKit fixes and will likely be available 
next week.


-- Kevin


Matthieu BROUILLARD wrote:

Hi all,

In our application that integrates some webapps we are facing quite the
same error than the one reported at
https://bugs.openjdk.java.net/browse/JDK-8149738.
The issue above has been marked with 'bugdb_22696741' ; does it mean it is
referenced with more details elsewhere? Is there a known workaround?

In our use case, when navigating in the webview into some GWT based
application using 8u74-i586 (or 8u60-i586) we always crash the JVM and
using 8u74 (64 bits) everything works.
Doing additional tests revealed that 8u45-b51-i586 is working ; but
unfortunately we have already moved on to more recent JDKs for our entire
application.

Sadly I do not have a simple reproduction app to provide.
We also enable some prism debug settings without seeing anything relevant
in the logs ; activating the software pipeline didn't changed anything
neither.

Are there specific debug params for the webview, webkit & jfxwebkit.dll ?

The crash report looks the same than in the above issue:

# # # # # # # # # # # # # # # # #

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x5456b7c9, pid=5836,
tid=6260
#
# JRE version: Java(TM) SE Runtime Environment (8.0_74-b02) (build
1.8.0_74-b02)
# Java VM: Java HotSpot(TM) Client VM (25.74-b02 mixed mode windows-x86 )
# Problematic frame:
# C  [jfxwebkit.dll+0x8eb7c9]
...
#

---  T H R E A D  ---

Current thread (0x0563d000):  JavaThread "JavaFX Application Thread"
[_thread_in_native, id=6260, stack(0x05c7,0x05cc)]

siginfo: ExceptionCode=0xc005, reading address 0x002e0060

Registers:
EAX=0x002e0030, EBX=0x0011, ECX=0x0d457870, EDX=0x
ESP=0x05cbd578, EBP=0x, ESI=0x0d457870, EDI=0x0bae3030
EIP=0x5456b7c9, EFLAGS=0x00210246

Top of Stack: (sp=0x05cbd578)
0x05cbd578:   0d202f60 54580e41 0001 0001
...
0x05cbd5e8:   54a51a88  54510e95 0d2f89a0

Instructions: (pc=0x5456b7c9)
0x5456b7a9:   24 0c 01 75 35 8b 4e 14 8b c1 c1 e8 09 a8 01 75
...
0x5456b7d9:   06 74 07 8b ce e8 4d de ff ff 5e c2 08 00 cc cc


Register to memory mapping:

EAX=0x002e0030 is an unknown value
EBX=0x0011 is an unknown value
ECX=0x0d457870 is an unknown value
EDX=0x is an unknown value
ESP=0x05cbd578 is pointing into the stack for thread: 0x0563d000
EBP=0x is an unknown value
ESI=0x0d457870 is an unknown value
EDI=0x0bae3030 is an unknown value


Stack: [0x05c7,0x05cc],  sp=0x05cbd578,  free space=309k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
C  [jfxwebkit.dll+0x8eb7c9]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.sun.webkit.WebPage.twkProcessMouseEvent(JIIIZF)Z+0
j
 
com.sun.webkit.WebPage.dispatchMouseEvent(Lcom/sun/webkit/event/WCMouseEvent;)Z+141
j
 
javafx.scene.web.WebView.processMouseEvent(Ljavafx/scene/input/MouseEvent;)V+175
j
 
javafx.scene.web.WebView.lambda$registerEventHandlers$32(Ljavafx/scene/input/MouseEvent;)V+2
j  javafx.scene.web.WebView$$Lambda$87.handle(Ljavafx/event/Event;)V+8
j
 
com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(Ljavafx/event/Event;)V+5
j
 
com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(Ljavafx/event/Event;)V+28
j
 
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/EventType;Ljavafx/event/Event;)Ljavafx/event/Event;+29
j
 
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+8
j
 
com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+11
j
 
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+29
j
 
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
 
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17
j
 
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
 
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17
j
 
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
 
com.sun.javafx.event.EventUtil.fireEventImpl(Ljavafx/event/EventDispatchChain;Ljavafx/event/EventTarget;Ljavafx/event/Event;)Ljavafx/event/Event;+10
j

Re: status behind JDK-8149738

2016-04-11 Thread Vadim Pakhnushev


Matthieu,

It's unlikely that your problem is the same as in the JDK-8149738.
You see, your crash is due to "reading address 0x002e0060" and in the 
JDK-8149738 it's "writing address 0xbbadbeef".

So they are not the same.

Vadim

On 11.04.2016 19:39, Matthieu BROUILLARD wrote:

Hi all,

In our application that integrates some webapps we are facing quite the
same error than the one reported at
https://bugs.openjdk.java.net/browse/JDK-8149738.
The issue above has been marked with 'bugdb_22696741' ; does it mean it is
referenced with more details elsewhere? Is there a known workaround?

In our use case, when navigating in the webview into some GWT based
application using 8u74-i586 (or 8u60-i586) we always crash the JVM and
using 8u74 (64 bits) everything works.
Doing additional tests revealed that 8u45-b51-i586 is working ; but
unfortunately we have already moved on to more recent JDKs for our entire
application.

Sadly I do not have a simple reproduction app to provide.
We also enable some prism debug settings without seeing anything relevant
in the logs ; activating the software pipeline didn't changed anything
neither.

Are there specific debug params for the webview, webkit & jfxwebkit.dll ?

The crash report looks the same than in the above issue:

# # # # # # # # # # # # # # # # #

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x5456b7c9, pid=5836,
tid=6260
#
# JRE version: Java(TM) SE Runtime Environment (8.0_74-b02) (build
1.8.0_74-b02)
# Java VM: Java HotSpot(TM) Client VM (25.74-b02 mixed mode windows-x86 )
# Problematic frame:
# C  [jfxwebkit.dll+0x8eb7c9]
...
#

---  T H R E A D  ---

Current thread (0x0563d000):  JavaThread "JavaFX Application Thread"
[_thread_in_native, id=6260, stack(0x05c7,0x05cc)]

siginfo: ExceptionCode=0xc005, reading address 0x002e0060

Registers:
EAX=0x002e0030, EBX=0x0011, ECX=0x0d457870, EDX=0x
ESP=0x05cbd578, EBP=0x, ESI=0x0d457870, EDI=0x0bae3030
EIP=0x5456b7c9, EFLAGS=0x00210246

Top of Stack: (sp=0x05cbd578)
0x05cbd578:   0d202f60 54580e41 0001 0001
...
0x05cbd5e8:   54a51a88  54510e95 0d2f89a0

Instructions: (pc=0x5456b7c9)
0x5456b7a9:   24 0c 01 75 35 8b 4e 14 8b c1 c1 e8 09 a8 01 75
...
0x5456b7d9:   06 74 07 8b ce e8 4d de ff ff 5e c2 08 00 cc cc


Register to memory mapping:

EAX=0x002e0030 is an unknown value
EBX=0x0011 is an unknown value
ECX=0x0d457870 is an unknown value
EDX=0x is an unknown value
ESP=0x05cbd578 is pointing into the stack for thread: 0x0563d000
EBP=0x is an unknown value
ESI=0x0d457870 is an unknown value
EDI=0x0bae3030 is an unknown value


Stack: [0x05c7,0x05cc],  sp=0x05cbd578,  free space=309k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
C  [jfxwebkit.dll+0x8eb7c9]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.sun.webkit.WebPage.twkProcessMouseEvent(JIIIZF)Z+0
j
  
com.sun.webkit.WebPage.dispatchMouseEvent(Lcom/sun/webkit/event/WCMouseEvent;)Z+141
j
  
javafx.scene.web.WebView.processMouseEvent(Ljavafx/scene/input/MouseEvent;)V+175
j
  
javafx.scene.web.WebView.lambda$registerEventHandlers$32(Ljavafx/scene/input/MouseEvent;)V+2
j  javafx.scene.web.WebView$$Lambda$87.handle(Ljavafx/event/Event;)V+8
j
  
com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(Ljavafx/event/Event;)V+5
j
  
com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(Ljavafx/event/Event;)V+28
j
  
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/EventType;Ljavafx/event/Event;)Ljavafx/event/Event;+29
j
  
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+8
j
  
com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+11
j
  
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+29
j
  
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
  
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17
j
  
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
  
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17
j
  
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69
j
  
com.sun.javafx.event.EventUtil.fireEventImpl(Ljavafx/event/EventDispatchChain;Ljavafx/event/EventTarget;Ljavafx/event/Event;)Ljavafx/event/Event;+10
j
  
com.sun.javafx.event.EventUtil.fireEvent(Ljavafx/event/EventTarget;Ljavafx/event/Event;)Ljavafx/event/Event;+46
j

Re: status behind JDK-8149738

2016-04-11 Thread Matthieu BROUILLARD

Kevin, Vadim,

thanks for the quick reply.

I tested with 1.8.0_102-ea-b01 (32 bits) and it still fails.

@Kevin what kind of report would you like me to generate? how to obtain the
native stack trace? I tried to set `-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=SOME_PATH` but the crash does not generate anything except
an hs_err file (
https://gist.github.com/McFoggy/5371c8409dde065aa7f017b7a00d32ec).

Re: status behind JDK-8149738

2016-04-11 Thread Kevin Rushforth


> is "writing address 0xbbadbeef".  So they are not the same.

Good catch, Vadim.

This is likely an OOM or some other internal failure. That is the 
tell-tale sign of a call to the internal abort . The fact that this 
works with 64-bit and fails with 32-bit suggests an OOM problem.


-- Kevin



Vadim Pakhnushev wrote:

Matthieu,

It's unlikely that your problem is the same as in the JDK-8149738.
You see, your crash is due to "reading address 0x002e0060" and in the 
JDK-8149738 it's "writing address 0xbbadbeef".

So they are not the same.

Vadim

On 11.04.2016 19:39, Matthieu BROUILLARD wrote:

Hi all,

In our application that integrates some webapps we are facing quite the
same error than the one reported at
https://bugs.openjdk.java.net/browse/JDK-8149738.
The issue above has been marked with 'bugdb_22696741' ; does it mean 
it is

referenced with more details elsewhere? Is there a known workaround?

In our use case, when navigating in the webview into some GWT based
application using 8u74-i586 (or 8u60-i586) we always crash the JVM and
using 8u74 (64 bits) everything works.
Doing additional tests revealed that 8u45-b51-i586 is working ; but
unfortunately we have already moved on to more recent JDKs for our 
entire

application.

Sadly I do not have a simple reproduction app to provide.
We also enable some prism debug settings without seeing anything 
relevant

in the logs ; activating the software pipeline didn't changed anything
neither.

Are there specific debug params for the webview, webkit & 
jfxwebkit.dll ?


The crash report looks the same than in the above issue:

# # # # # # # # # # # # # # # # #

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x5456b7c9, pid=5836,
tid=6260
#
# JRE version: Java(TM) SE Runtime Environment (8.0_74-b02) (build
1.8.0_74-b02)
# Java VM: Java HotSpot(TM) Client VM (25.74-b02 mixed mode 
windows-x86 )

# Problematic frame:
# C  [jfxwebkit.dll+0x8eb7c9]
...
#

---  T H R E A D  ---

Current thread (0x0563d000):  JavaThread "JavaFX Application Thread"
[_thread_in_native, id=6260, stack(0x05c7,0x05cc)]

siginfo: ExceptionCode=0xc005, reading address 0x002e0060

Registers:
EAX=0x002e0030, EBX=0x0011, ECX=0x0d457870, EDX=0x
ESP=0x05cbd578, EBP=0x, ESI=0x0d457870, EDI=0x0bae3030
EIP=0x5456b7c9, EFLAGS=0x00210246

Top of Stack: (sp=0x05cbd578)
0x05cbd578:   0d202f60 54580e41 0001 0001
...
0x05cbd5e8:   54a51a88  54510e95 0d2f89a0

Instructions: (pc=0x5456b7c9)
0x5456b7a9:   24 0c 01 75 35 8b 4e 14 8b c1 c1 e8 09 a8 01 75
...
0x5456b7d9:   06 74 07 8b ce e8 4d de ff ff 5e c2 08 00 cc cc


Register to memory mapping:

EAX=0x002e0030 is an unknown value
EBX=0x0011 is an unknown value
ECX=0x0d457870 is an unknown value
EDX=0x is an unknown value
ESP=0x05cbd578 is pointing into the stack for thread: 0x0563d000
EBP=0x is an unknown value
ESI=0x0d457870 is an unknown value
EDI=0x0bae3030 is an unknown value


Stack: [0x05c7,0x05cc],  sp=0x05cbd578,  free space=309k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, 
C=native

code)
C  [jfxwebkit.dll+0x8eb7c9]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.sun.webkit.WebPage.twkProcessMouseEvent(JIIIZF)Z+0
j
  
com.sun.webkit.WebPage.dispatchMouseEvent(Lcom/sun/webkit/event/WCMouseEvent;)Z+141 


j
  
javafx.scene.web.WebView.processMouseEvent(Ljavafx/scene/input/MouseEvent;)V+175 


j
  
javafx.scene.web.WebView.lambda$registerEventHandlers$32(Ljavafx/scene/input/MouseEvent;)V+2 


j  javafx.scene.web.WebView$$Lambda$87.handle(Ljavafx/event/Event;)V+8
j
  
com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(Ljavafx/event/Event;)V+5 


j
  
com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(Ljavafx/event/Event;)V+28 


j
  
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/EventType;Ljavafx/event/Event;)Ljavafx/event/Event;+29 


j
  
com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+8 


j
  
com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+11 


j
  
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+29 


j
  
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69 


j
  
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17 


j
  
com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Ljavafx/event/Event;)Ljavafx/event/Event;+69 


j
  
com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Ljavafx/event/Event;Ljavafx/event/EventDispatchChain;)Ljavafx/event/Event;+17 


j

9-dev unlocked following sanity testing

2016-04-11 Thread Kevin Rushforth

[9]: : [packager] Module Path Packager Arguments

2016-04-11 Thread Chris Bensen

Kevin,

Please review. This adds new argument to Java Packager, the Minesweeper FX 
Appstore App and cleans a lot of things up. My Packager sandbox will be in sync 
with 9dev except for refactoring changes.

https://bugs.openjdk.java.net/browse/JDK-8150991 

http://cr.openjdk.java.net/~cbensen/JDK-8150991/webrev.02 


Chris

Re: RFR: JDK-8075550 - Error "JavaFX runtime not found" in nashorn when load predefines scripts to import JavaFX packages

[9] Review request for 8150181: javafx print jobs take 60 times longer than javax.print

Re: RFR: JDK-8075550 - Error "JavaFX runtime not found" in nashorn when load predefines scripts to import JavaFX packages

Re: RFR: JDK-8075550 - Error "JavaFX runtime not found" in nashorn when load predefines scripts to import JavaFX packages

status behind JDK-8149738

Re: status behind JDK-8149738

Re: status behind JDK-8149738

Re: status behind JDK-8149738

Re: status behind JDK-8149738

9-dev unlocked following sanity testing

[9]: : [packager] Module Path Packager Arguments

11 matches

Site Navigation

Mail list logo

Footer information