VMware Horizon Community
sappomannoz
Hot Shot
Hot Shot
Jump to solution

Java 8u60 and crashes

‌Hello,

after updating my  test view Windows 7 environment to view 6.2 I noticed that net beans was crashing after some seconds or minutes of use.

stacktrace starting with awt.dll and then going in thru the VMware 3D video driver.

I tried to downgrade the agent to 6.1.1 but I couldn't even connect to a desktop. The only other thing I changed was the version of the java sdk, going from 8u51 to 8u60. Now I'm using agent 6.2 with java 8u51 whitout issues. I'm the only one with those issues?

Cristiano

Reply
0 Kudos
1 Solution

Accepted Solutions
jksnbco
Enthusiast
Enthusiast
Jump to solution

Update - on the parent VM, I powered it off, edited settings and enabled 3d support.  We do not have a 3D card in any of our hosts, so this had previously been disabled.  When we previously had software 3d rendering enabled, we had some performance issues with Windows 7.  We disabled the 'Desktop windows Manager session manager' server on the template and it seems like performance is acceptable now.

With 3D support enabled on the parent template and view agent 6.2 / Tools 9.10.5.2981885 installed, our Java app has not crashed.

Side note - if Tools 9.10.5.2981885 is installed and agent 6.01 is installed, users cannot log in.  Black screen appears.  I am assuming this is why View 6.2 / Agent 6.2 is required for ESXi 6 update 1.

View solution in original post

Reply
0 Kudos
14 Replies
sappomannoz
Hot Shot
Hot Shot
Jump to solution

It crashes also with java 8u51. Smiley Sad

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

We are also seeing this problem after updating from agent 6.01 to 6.2

I have done a 'clean' install of Windows 7 x86 (problem doesn't seem to occur on x64 - haven't fully tested yet).  No windows updates.  Java 8 update60 installed.  .  Tools Version 9.10.5.2981885 and Agent 6.2.  Same problem occurs - java app crashes.

Log Name:      Application

Source:        Application Error

Date:          9/16/2015 5:52:32 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      test

Description:

Faulting application name: java.exe, version: 8.0.600.27, time stamp: 0x55c0ff1a

Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96e

Exception code: 0xc0000374

Fault offset: 0x000c37b7

Faulting process id: 0xcd4

Faulting application start time: 0x01d0f0e304100c58

Faulting application path: C:\Program Files\Java\jre1.8.0_60\bin\java.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 602ad3b0-5cd6-11e5-a5ea-005056a9a341

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-09-17T00:52:32.000000000Z" />

    <EventRecordID>310</EventRecordID>

    <Channel>Application</Channel>

    <Computer>test</Computer>

    <Security />

  </System>

  <EventData>

    <Data>java.exe</Data>

    <Data>8.0.600.27</Data>

    <Data>55c0ff1a</Data>

    <Data>ntdll.dll</Data>

    <Data>6.1.7601.17514</Data>

    <Data>4ce7b96e</Data>

    <Data>c0000374</Data>

    <Data>000c37b7</Data>

    <Data>cd4</Data>

    <Data>01d0f0e304100c58</Data>

    <Data>C:\Program Files\Java\jre1.8.0_60\bin\java.exe</Data>

    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>

    <Data>602ad3b0-5cd6-11e5-a5ea-005056a9a341</Data>

  </EventData>

</Event>

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

Uninstall agent / reboot, uninstall tools / reboot

Install old tools version from EXE - version 9.10.1.2791197 reboot

Install Agent 6.01 reboot

Java app does not seem to crash with Tools 9.10.1.2791197 / Agent 6.0.1

Reply
0 Kudos
grossag
VMware Employee
VMware Employee
Jump to solution

Does it reproduce in a way that it just sits at a crash dialog?  If so, can you download procdump from sysinternals ( ProcDump ) then run "procdump -ma <pid>" to create a full process dump?

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

I can't make it happen reliably, but I can try this method.

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

Command used "procdump.exe -t -ma java.exe"

I then used windbg.exe to analyze.  It looks like it may be related to the new graphic driver - not 100% sure.  I have opened a case with VMware.

 

0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for jvm.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for awt.dll -

FAULTING_IP:
+0
00000000 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  00000000 -- (.cxr 0x0;r)
eax=00000000 ebx=00000001 ecx=33b1280d edx=0000000b esi=77687380 edi=77687340
eip=775f70b4 esp=44eee3e4 ebp=44eee400 iopl=0         nv up ei pl zr na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
ntdll!KiFastSystemCallRet:
775f70b4 c3              ret

FAULTING_THREAD:  00000ce0

PROCESS_NAME:  java.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

APP:  java.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

LAST_CONTROL_TRANSFER:  from 775f68d4 to 775f70b4

BUGCHECK_STR:  APPLICATION_FAULT_ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_SHUTDOWN

PRIMARY_PROBLEM_CLASS:  ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_SHUTDOWN

DEFAULT_BUCKET_ID:  ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_SHUTDOWN

STACK_TEXT: 
7768ce10 7762ddbf ntdll!RtlFreeHeap+0x64
7768ce14 762fbbe4 kernel32!HeapFree+0x14
7768ce18 6b869a1d vm3dgl!unloaded+0x859a1d
7768ce1c 6b01deb9 vm3dgl!unloaded+0xdeb9
7768ce20 6b01dee6 vm3dgl!unloaded+0xdee6
7768ce24 6b869d83 vm3dgl!unloaded+0x859d83
7768ce28 776089d8 ntdll!LdrpCallInitRoutine+0x14
7768ce2c 77615c41 ntdll!LdrpRunInitializeRoutines+0x26f
7768ce30 7761052e ntdll!LdrpLoadDll+0x4d1
7768ce34 7761232c ntdll!LdrLoadDll+0x92
7768ce38 759b88ee kernelbase!LoadLibraryExW+0x15a
7768ce3c 76303c12 kernel32!LoadLibraryW+0x11
7768ce40 6c7eae06 opengl32!unloaded+0x3ae06
7768ce44 6c7eb0f3 opengl32!unloaded+0x3b0f3
7768ce48 6c7eb1a9 opengl32!unloaded+0x3b1a9
7768ce4c 6c7ec6a4 opengl32!unloaded+0x3c6a4
7768ce50 6c7f5658 opengl32!unloaded+0x45658
7768ce54 6c7f5dd4 opengl32!unloaded+0x45dd4
7768ce58 75b16868 gdi32!DescribePixelFormat+0x2e
7768ce5c 6c989f1b awt!Java_sun_awt_Win32GraphicsDevice_getMaxConfigsImpl+0x35


FOLLOWUP_IP:
awt!Java_sun_awt_Win32GraphicsDevice_getMaxConfigsImpl+35
6c989f1b 8bf8            mov     edi,eax

SYMBOL_STACK_INDEX:  13

SYMBOL_NAME:  awt!Java_sun_awt_Win32GraphicsDevice_getMaxConfigsImpl+35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: awt

IMAGE_NAME:  awt.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  55c10a47

STACK_COMMAND:  dps 7768ce10 ; kb

FAILURE_BUCKET_ID:  ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_SHUTDOWN_80000003_awt.dll!Java_sun_awt_Win32GraphicsDevice_getMaxConfigsImpl

BUCKET_ID:  APPLICATION_FAULT_ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_SHUTDOWN_awt!Java_sun_awt_Win32GraphicsDevice_getMaxConfigsImpl+35

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:actionable_heap_corruption_heap_failure_block_not_busy_shutdown_80000003_awt.dll!java_sun_awt_win32graphicsdevice_getmaxconfigsimpl

FAILURE_ID_HASH:  {59b5c559-7f87-ae47-d222-d22dcd4c0bb4}

Followup: MachineOwner
---------

Reply
0 Kudos
WilliamReid
Enthusiast
Enthusiast
Jump to solution

@jksnbo - Can you PM me your SR?

Also - for confirmation, can we confirm if the View agent is required to reproduce?

I'm assisting another customer who indicates it's reproducible without the Agent using the latest tools...

Thanks,

Wm

Reply
0 Kudos
sappomannoz
Hot Shot
Hot Shot
Jump to solution

Hello,

I got this form support

1 - Turn on the parent VM  and login

2 - Uninstall VMware agent and reboot

3 - Uninstall VMware tools and reboot

4 - Install VMware tools without installing the VGA driver and shutdown

5 - Turn on VM Install VMware agent and shutdown

6 - Login back in and open CMD and type ipconfig /release and shutdown

7 - Take a snapshot and recompose the pool

The reason for the full shutdown is the changes that we have just made in the VM's VMX file will not be loaded if you simply reboot. It requires a full power down to reload the VMX file.


I'm trying it out right now. See also this thread:


New Horizon View 6.2 agent stops Blender software


UPDATE: didn't help, apps are still crashing

Cristiano

Reply
0 Kudos
sappomannoz
Hot Shot
Hot Shot
Jump to solution

Hello WilliamReid,

I installed blender form blender.org, also affected by this issue. It's easier to troubleshoot as it always crashes, see New Horizon View 6.2 agent stops Blender software

If I connect over PCoIP and broker blender crashes during startup. Same session via RDP blender starts w/o problems. I have also sent you the SR via PM

Kind regards

Cristiano

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

Update - on the parent VM, I powered it off, edited settings and enabled 3d support.  We do not have a 3D card in any of our hosts, so this had previously been disabled.  When we previously had software 3d rendering enabled, we had some performance issues with Windows 7.  We disabled the 'Desktop windows Manager session manager' server on the template and it seems like performance is acceptable now.

With 3D support enabled on the parent template and view agent 6.2 / Tools 9.10.5.2981885 installed, our Java app has not crashed.

Side note - if Tools 9.10.5.2981885 is installed and agent 6.01 is installed, users cannot log in.  Black screen appears.  I am assuming this is why View 6.2 / Agent 6.2 is required for ESXi 6 update 1.

Reply
0 Kudos
sappomannoz
Hot Shot
Hot Shot
Jump to solution

Hello @jksnbcojksnbco

thank you for sharing. I will try this tomorrow!

Cristiano

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

@WilliamReid - I'm not sure how to PM you.

The issue does occur without agent, just tools being installed.

Reply
0 Kudos
sappomannoz
Hot Shot
Hot Shot
Jump to solution

HI jksnbco

it works also for me, thank you

Cristiano

Reply
0 Kudos
jksnbco
Enthusiast
Enthusiast
Jump to solution

VMTools 10.0.5 seems to fix this problem.  It includes a new video driver.  3d settings no longer have to be enabled.

The VMtools 10.0.0 VMWARE SVGA 3d driver version 8.15.1.32
dated 7/15/2015


The VM tools 10.0.5 VMWARE SVGA 3d driver version is 8.15.1.33
dated 10/16/2015

I haven't fully tested yet, but so far the app I had been using has not crashed.

Reply
0 Kudos