Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client memory leak if Win32 client 0.14+ runs inside a RDP session #696

Closed
totaam opened this issue Sep 27, 2014 · 13 comments
Closed

Client memory leak if Win32 client 0.14+ runs inside a RDP session #696

totaam opened this issue Sep 27, 2014 · 13 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Sep 27, 2014

Issue migrated from trac ticket # 696

component: platforms | priority: minor | resolution: wontfix | keywords: win32

2014-09-27 12:22:59: totaam created the issue


Split from #684#comment:10.

@totaam
Copy link
Collaborator Author

totaam commented Sep 28, 2014

2014-09-28 16:00:19: totaam changed owner from antoine to sschnitzer

@totaam
Copy link
Collaborator Author

totaam commented Sep 28, 2014

2014-09-28 16:00:19: totaam commented


I cannot reproduce, I've tried an XP 32 bit client and a Windows 7 64 bit client. I've tried turning opengl off, sound on and off, changing encodings, etc..

Please provide more details.
Maybe also try the latest windows beta build to see if it helps. (some of the earlier beta builds had a broken opengl initializations, which would have caused it to revert to cairo / GTK rendering)

@totaam
Copy link
Collaborator Author

totaam commented Oct 27, 2014

2014-10-27 18:10:00: totaam commented


More info on this was added to #684

@totaam
Copy link
Collaborator Author

totaam commented Nov 4, 2014

2014-11-04 20:23:25: sschnitzer commented


This is a follow up to the question on #684.
I tried to evaluated if memory consumption growth depends on the encoding. Unfortunately, I currently can only log in remotely via RDP to the Windows machine. It seems that the RDP connection significantly impacts this evaluation. I will continue trying to get some reasonable results on that, which might take a few weeks.
Can the ticket stay open that long?
Is there anything else I can do?

@totaam
Copy link
Collaborator Author

totaam commented Nov 5, 2014

2014-11-05 01:52:13: totaam commented


No problem with keeping this ticket open a bit longer. If the leak only ever happens with RDP.. chances are that this is part of the problem.

Once you have more info, please edit this ticket title to better reflect the cause of the problem: is the use of a proxy server required or not? RDP required? Encodings? Sound? opengl? etc.

@totaam
Copy link
Collaborator Author

totaam commented Dec 4, 2014

2014-12-04 17:46:24: totaam commented


Any update? Should this be a blocker for 0.15?

@totaam
Copy link
Collaborator Author

totaam commented Dec 14, 2014

2014-12-14 19:15:22: sschnitzer changed title from memory leak in win32 0.15 beta client to Client memory leak if Win32 client 0.14+ runs inside a RDP session

@totaam
Copy link
Collaborator Author

totaam commented Dec 14, 2014

2014-12-14 19:15:22: sschnitzer commented


I did some further tests, observations follow.
a) encoding=rgb did not have any noticeable effect on the leak.
b) It definitely only occurs if the xpra client is executed within a RDP session. If I reconnect to a crashed session on a native Windows 7, the leak doesn't occur any more. My setup: Xpra-Server with Xpra-Proxy on Centos-7 <-> Windows-7 RDP-Server <-> Win7-RDP-Client or xfreerdp on Linux.
c) I reproduced this with 0.14.10 client and server and also with Windows client r8235 and Linux server r8249.

@totaam
Copy link
Collaborator Author

totaam commented Dec 26, 2014

2014-12-26 03:51:19: antoine changed priority from critical to minor

@totaam
Copy link
Collaborator Author

totaam commented Dec 26, 2014

2014-12-26 03:51:19: antoine commented


Have you tried turning opengl off? Does re-connecting via RDP change anything, etc..

Lowering the priority because it looks like a bug in RDP or windows. I've also added links in the FAQ: [/wiki/FAQ?action=diff&version=64]

@totaam
Copy link
Collaborator Author

totaam commented Feb 13, 2015

2015-02-13 04:53:58: totaam changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Feb 13, 2015

2015-02-13 04:53:58: totaam set resolution to wontfix

@totaam
Copy link
Collaborator Author

totaam commented Feb 13, 2015

2015-02-13 04:53:58: totaam commented


Not heard back, closing. Feel free to reopen if you can reproduce without RDP and with our latest builds. Otherwise... I doubt there's much we can do.

@totaam totaam closed this as completed Feb 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant