[SRU] fcitx 100% CPU usage on rare case
Bug #1652591 reported by
Aron Xu
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fcitx (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Aron Xu |
Bug Description
[Impact]
There is a rare case that fcitx runs at 100% CPU when using Sogou Pinyin input method that sometimes happen after suspend/resume, even though the problem does not break client usages, it will drain battery of laptop and makes fan very noisy.
[Test Case]
After upgrading the package, user will not see 100% CPU usage of fcitx after frequent suspend/resume.
[Regression Potential]
The patch limits the call of accept() to be less than 21 times, and the calling code already has error handling when the returning value is less than 0, so the possibility of regression is minimal.
Changed in fcitx (Ubuntu): | |
status: | New → Fix Released |
Changed in fcitx (Ubuntu Yakkety): | |
status: | New → In Progress |
assignee: | nobody → Aron Xu (happyaron) |
Changed in fcitx (Ubuntu Xenial): | |
status: | New → In Progress |
tags: |
added: verification-done-xenial removed: verification-needed |
To post a comment you must log in.
Hello Aron, or anyone else affected,
Accepted fcitx into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ fcitx/1: 4.2.9.1- 1ubuntu1. 16.04.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!