Bug 1251730 - RDP session is frozen, CPU is used till 100%
RDP session is frozen, CPU is used till 100%
Product: Fedora
Classification: Fedora
Component: freerdp (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Mads Kiilerich
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-09 06:17 EDT by Sergei LITVINENKO
Modified: 2016-12-20 09:21 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 09:21:59 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
top info (36.94 KB, image/png)
2015-11-21 13:44 EST, Sergei LITVINENKO
no flags Details

  None (edit)
Description Sergei LITVINENKO 2015-08-09 06:17:52 EDT
Description of problem:
xfreerdp and xorg can use a lot of CPU (till 100%) and remote screen is frozen

Version-Release number of selected component (if applicable):

How reproducible:
50%. In case of first connect to remore system is problem, second connect in 90% is problem too.

Steps to Reproduce:
1. xfreerdp -decorations +clipboard /w:1600 /h:1170 /u:*** /v:*** /p:***

Actual results:
Remote session is frozen, CPU is 100% used. Usually, next connect in 90% will be frozen too

Expected results:
CPU is used according to real needs, remote session work as expected (interactivity is depend of internet channel speed).

Additional info:
Remote OS is Win7Pro.
It is looks like parameter +clipboard cause issue
Comment 1 Sergei LITVINENKO 2015-11-21 03:11:49 EST
Issue still present in F23

Actual package is freerdp-1.2.0-0.9.git.24a752a.fc23.x86_64

When issue is occurred, 2 processed use CPU very much
 1. Xorg use 100%
 2. xfreerdp 70-80%

Affected both my hosts

  1. Desktop: F23  64-bit (nouveau)


  2. Laptop:  F23  32-bit (i915)

Comment 2 Sergei LITVINENKO 2015-11-21 13:44 EST
Created attachment 1097485 [details]
top info
Comment 3 Fedora End Of Life 2016-11-24 07:16:50 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2016-12-20 09:21:59 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.