Enterprise Client Community

THANKS FOR ALL HAVING SENT FEEDBACK!!!

It seems that what Roland Heinrichs found is true: without setting parameters "-dsa -Xnoclassgc" the client works stable. You have to remove BOTH parameters, one is not enough.

So once again:
THANKS to all of you!
SPECIAL THANKS to Roland!
...............................................................................

Hi,

you may have already read in the forum that there is a problem with Java 8.40, 32bit - the VM (== the client) suddenly crashed.

I now wrote a program to reproduce. THe program is available on the CaptainCasa demo server (in the demo workplace).

Please find the instructions what to do here: http://www.CaptainCasa.com/pdf/20150326_javavmcrash.pdf

If you run Java 8.40 32bit: please run the program and report back the counter in the demo application, that is reached. Just add your counter to this forum post so that we can collect.

THANKS!!!!
Björn

PLEASE DO NOT USED THIS POST FOR DISCUSSIONS ON WORKAROUNDS. THERE IS A SECOND POST IN THE DEPLOYMENT SECTION OF THE FORUM. I WOULD LIKE TO ONLY COLLECT FEEDBACK HERE. THANKS!

Hi!

The bug is reproducable. Please find attached the log informations.
If you need additional informations, just let me know.

regards
Roland

could reproduce the problem on several computers.
Counters reached from 1 to ca. 50.
However on one faster Computer (3.3GHz i5) starting the "chaos" and then doing absolutely nothing (no mouse movements, no YouTube Videos,..) the Counter once reached 180.

good to know:
starting this as Applet (...startdemos.html) does not show the crash, also when using the 64bit Version the chaos seems to be stable.

Manfred

I add the following response that I received via eMail:

Java 8 Update 40 (Build 1.8.0_40-b26)

3 attempts:
2 x crashed after 3. iteration
1 x crashed after 6. iteration

no problems with Java 1.7.0_71

Browser was Chrome 41.0.2272.101m

Ok, try to remove start parameters: -dsa -Xnoclassgc

With startparameter (-dsa -Xnoclassgc):
java -dsa -Xnoclassgc -cp eclnt.jar org.eclnt.client.page.PageWebStart http://www.captaincasademo.com/ccdemos/ faces/workplace/workplace.jsp

2015:03:26 09:48:14:307 | 15 | INFO | ++++++++++ unblock() called .......... org.eclnt.client.lookandfeel.Captai
nCasaScrollBarUI>unblock
2015:03:26 09:48:14:307 | 15 | INFO | ADJUSTMENT: execute scrolling .......... org.eclnt.client.elements.impl.ut
il.ServerSideScrollingAreaScrollListener>processAdjustment
2015:03:26 09:48:14:308 | 15 | INFO | updateSbVisibleAmount 18 .......... org.eclnt.client.controls.impl.ServerS
ideScrollingArea>updateSbVisibleAmount
2015:03:26 09:48:14:308 | 15 | INFO | setSbParams: 100/18/0 .......... org.eclnt.client.controls.impl.ServerSide
ScrollingArea>setSbParams
2015:03:26 09:48:14:309 | 15 | INFO | #################### Layouting of grid is executed #################### ..
........ org.eclnt.client.controls.layout.FlexGridLayout>layoutContainer
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x520c4e3e, pid=6344, tid=7424
#
# JRE version: Java(TM) SE Runtime Environment (8.0_40-b26) (build 1.8.0_40-b26)
# Java VM: Java HotSpot(TM) Client VM (25.40-b25 mixed mode, sharing windows-x86

# Problematic frame:
# V [jvm.dll+0xb4e3e]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Roland\Downloads\hs_err_pid6344.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#

C:\Users\Roland\Downloads>rem java -cp eclnt.jar org.eclnt.client.page.PageWebStart http://www.captaincasademo.com/ccdem
os/ faces/workplace/workplace.jsp

Without it seems running fine. ;-)
regards

COULD WE TRY TO NOT DISCUSS POSSIBLE SOLUTIONS IN THIS POST? I WANT TO COLLECT THE FEEDBACK. THERE IS A SECOND POST IN THE DEPLYOMENT-SECTION WHERE WE CAN DISCUSS IF SOMEONE HAS WORKAROUNDS. THANKS!!!

But your statement seems to be very goooooood...(?)

Roland, I should have mentioned this in my top statement - sorry! Blame is on my side... Björn

Browser: Firefox 36.0.3

Java Web Start 11.31.2.13
Using JRE version 1.8.0_31-b13 Java HotSpot(TM) Client VM
=> counter reached 3541 (and I ended chaos)

Java Web Start 11.40.2.26
Using JRE version 1.8.0_40-b26 Java HotSpot(TM) Client VM
=> counter reached 9 (and crashed)
=> counter reached 4 (and crashed)
=> counter reached 15 (and crashed)

After disabling 1.8.0_40 again...

Java Web Start 11.40.2.26
Using JRE version 1.8.0_31-b13 Java HotSpot(TM) Client VM
=> counter reached 5443 (and I ended chaos)

Chrome: Version 41.0.2272.101 m

Java Web Start 11.40.2.25
JRE-Version verwenden 1.8.0_40-b25 Java HotSpot(TM) Client VM

run 1: 72
run 2: 0 -> did crash while navigating to the test
run 3: 176

FireFox 36.0.4
JRE-Version 1.8.0_40-b26 (32-Bit)
Java Web Start 11.40.2.26

These are my chaos results:
7
7
12
5
179
1
89
181
5
8

Best regards
Frauke

Firefox 36.0.4
Java 1.8.0_40-b26 32bit
Windows 7 Pro 64bit

Results (count)
0 (crashed while navigating)
1
5
5
2
0
0 (crashed while navigating)
5
2
2

Gruss, Thomas

THANKS FOR ALL HAVING SENT FEEDBACK!!!

It seems that what Roland Heinrichs found is true: without setting parameters "-dsa -Xnoclassgc" the client works stable. You have to remove BOTH parameters, one is not enough.

So once again:
THANKS to all of you!
SPECIAL THANKS to Roland!

(This text was also added to the original post, so that the text is on the top.)