X2Go Bug report logs - #1167
Windows 7 runtime error - R6025 - pure virtual function, kills x2go client after Windows screen lock/unlock

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: "Petronic, Mark" <Mark.Petronic@hughes.com>

Date: Wed, 29 Mar 2017 16:40:01 UTC

Severity: normal

Found in version 4.1.0.0

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1167; Package x2goclient. (Wed, 29 Mar 2017 16:40:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Petronic, Mark" <Mark.Petronic@hughes.com>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Wed, 29 Mar 2017 16:40:02 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.x2go.org (full text, mbox):

From: "Petronic, Mark" <Mark.Petronic@hughes.com>
To: "submit@bugs.x2go.org" <submit@bugs.x2go.org>
Subject: Windows 7 runtime error - R6025 - pure virtual function, kills x2go client after Windows screen lock/unlock
Date: Wed, 29 Mar 2017 15:04:14 +0000
[Message part 1 (text/plain, inline)]
Package: x2goclient
Version: 4.1.0.0


Steps to reproduce:



1. Fire up x2go client

2. Establish a session

3. Session starts fine and all is well

3. Stop working and walk away and, due to IT policy, Windows screen will lock after 15 minutes of inactivity

4. Ctrl-Alt-Delete and log back into Windows

5. Find a popup error dialog indicating vcxsrv.exe crashed. The runtime error Windows popup message dialog says:



=========================================================

Microsoft Visual C++ Runtime Library

Program:

C:\Users\mpetronic\<path-to-my-install>\VcXsrv\vcxsrv.exe

R6025

- pure virtual function call

=========================================================

I can also force the crash if, after I establish a working x2go session, I Ctrl-Alt-Delete and lock my desktop manually. Same crash occurs when I log back in. To recover, I have to close the x2go client and restart it then I can restart my session. On the server side, my session is restarted just fine. Everything I had open there is restored. So, this is really annoying in that, every time I walk away from my PC for a short time, I know I have to reestablish all my sessions due to this crash.

I have further experimented and found this crash ONLY occurs when I run in -rootless configuration. I use that so that Alt-Tab works properly in my X session otherwise, when I Alt-Tab, I bounce back to windows in Windows. I basically use these settings set in the "X.Org Server Settings" dialog per (http://www.terheyden.com/blog/?p=202):
-rootless -notrayicon -clipboard -keyhook

Another tidbit of information is this crash only started to happen a few months ago but I made no changes to my x2go client installation or configuration. It started after a Windows update. Background: To access our remote systems at work, we have to use VMWare's VDI (Virtual Desktop Infrastructure). So, I have to first log into my corporate desktop, then start a VDI session using RSA key login, which gives me another Windows VDI desktop. On the VDI Windows instance, I have x2go installed in the portable way because I don't have admin access these to install it by running the setup program. Some months back, the VDI admins installed some Windows update per normal security patching. After that, this crash started happening. There happens to be a old VDI configuration that apparently has NOT been patched. If I log onto that instance, the crash does not occur. This crash happens with your latest version 4.1.0.0 and two previous versions so it appears to be related to something common to all versions. Since we still have this old (working) VDI configuration (until some realizes it and updates it) and new (broken) one, maybe there is a way I can help by getting you some information as to what is different between the two related to the Windows run time libraries installed?

I am glad to help in any way to get you information to help in debugging and fixing this issue. Please let me know what I can do to assist.

Thanks!



[cid:image001.png@01D2A87C.0E8D7B90]
[Message part 2 (text/html, inline)]
[image001.png (image/png, inline)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1167; Package x2goclient. (Fri, 19 May 2017 16:20:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Petronic, Mark" <Mark.Petronic@hughes.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Fri, 19 May 2017 16:20:02 GMT) Full text and rfc822 format available.

Message #10 received at 1167@bugs.x2go.org (full text, mbox):

From: "Petronic, Mark" <Mark.Petronic@hughes.com>
To: "1167@bugs.x2go.org" <1167@bugs.x2go.org>
Subject: More details
Date: Fri, 19 May 2017 14:44:19 +0000
[Message part 1 (text/plain, inline)]
We are running Windows 7 using VmWare Virtual Desktop (VDI). So, my x2go
client runs on that Windows desktop. The crash is actually happening in vcxsrv.ex
and I was able to obtain the following additional information:

(1) The VDI admins updated some VDI runtimes on our VDI desktop instances to
    VMWare version 6 around the time we started to experience this crash

(2) Here is a more detailed dump of some debug information I found:

Problem signature:
  Problem Event Name:  APPCRASH
  Application Name:  vcxsrv.exe
  Application Version:  1.17.0.0
  Application Timestamp: 55b5056a
  Fault Module Name:  vm3dum.dll
  Fault Module Version: 8.15.1.46
  Fault Module Timestamp: 57112640
  Exception Code:  40000015
  Exception Offset:  00026b27
  OS Version: 6.1.7601.2.1.0.256.4
  Locale ID: 1033
  Additional Information 1: f5d8
  Additional Information 2: f5d85880320133c2803765541f044878
  Additional Information 3: 4651
  Additional Information 4: 4651b47fc82bdc83b534297b987ba7e7




[Message part 2 (text/html, inline)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1167; Package x2goclient. (Sat, 20 May 2017 10:10:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to uli42@gmx.de:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sat, 20 May 2017 10:10:02 GMT) Full text and rfc822 format available.

Message #15 received at 1167@bugs.x2go.org (full text, mbox):

From: Ulrich Sibiller <ulrich.sibiller@gmail.com>
To: "Petronic, Mark" <Mark.Petronic@hughes.com>, 1167@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#1167: More details
Date: Sat, 20 May 2017 12:06:55 +0200
On Fri, May 19, 2017 at 4:44 PM, Petronic, Mark
<Mark.Petronic@hughes.com> wrote:
> vm3dum.dll

Googling for vm3dum.dll reveals a lot of crashes related to that
vmware dll. So I suppose it has nothing to do with x2go but with your
vmware. Some post suggest upgrading vmware-tools so please try that
and see if the crashes go away.

Also you could try moving the virtual machine to another host (or
maybe a vmware player or workstation) and check if the crashes
persist.

Uli


Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1167; Package x2goclient. (Sat, 20 May 2017 20:55:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Petronic, Mark" <Mark.Petronic@hughes.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sat, 20 May 2017 20:55:02 GMT) Full text and rfc822 format available.

Message #20 received at 1167@bugs.x2go.org (full text, mbox):

From: "Petronic, Mark" <Mark.Petronic@hughes.com>
To: "1167@bugs.x2go.org" <1167@bugs.x2go.org>, "uli42@gmx.de" <uli42@gmx.de>
Subject: Re: [X2Go-Dev] Bug#1167: More details
Date: Sat, 20 May 2017 20:52:51 +0000
[Message part 1 (text/plain, inline)]
Yes, I noticed the same thing when I was googling around for clues. We are running the latest version of vmware-tools and I believe, when we moved to vmware version 6 this started happening around that time but we were not able to correlate it then and a number of updates have been applied since then. I had the VM admins build me an image with the older version of the tools last week but I still experienced the crash. IMO, given the popup error refers to a crash related to a pure virtual function, it would seem that this very well might be breakage in some vmware DLL API that is not acting in a backwards compatible manner.  Just a guess. Also, this only occurs when I configure the vcxsrv in rootless mode. I might try your suggestion by trying to run the image on a player. I already know it happens on different hosts as we have a number of hosts supporting the VDI instances and we float around day to day. I've confirmed it happens on different hosts in that way. Thanks for you suggestions and input!


Mark

________________________________
From: Ulrich Sibiller <ulrich.sibiller@gmail.com>
Sent: Saturday, May 20, 2017 6:06:55 AM
To: Petronic, Mark; 1167@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#1167: More details

On Fri, May 19, 2017 at 4:44 PM, Petronic, Mark
<Mark.Petronic@hughes.com> wrote:
> vm3dum.dll

Googling for vm3dum.dll reveals a lot of crashes related to that
vmware dll. So I suppose it has nothing to do with x2go but with your
vmware. Some post suggest upgrading vmware-tools so please try that
and see if the crashes go away.

Also you could try moving the virtual machine to another host (or
maybe a vmware player or workstation) and check if the crashes
persist.

Uli

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Dec 13 15:30:23 2018; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.