原始文献 / 论坛帖 / Re: Runaway CPU usage for 64bit BitCoin (Linux Client)
Re: Runaway CPU usage for 64bit BitCoin (Linux Client)
Bitcointalk · 2010-07-14 18:45:53 UTC
一开始它会错误地把自己设成最低优先级，之后 generate 线程只在找到块的那一刻临时调一次优先级。找到块以后，你肯定想让它赶紧广播出去，越快越好，免得别人先找到、让你的块作废。generate 线程每隔几天才有不到一秒切到高优先级。
0.3.1 应该快发了。发布前还有几个问题要修。
引用自：knightmb，2010 年 7 月 12 日 10:39:13 PM（https://bitcointalk.org/index.php?topic=299.msg2409#msg2409）
顺带说下，另一个 GUI 问题我定位到了。
"最小化到托盘而不是任务栏"这个选项把我机器 CPU 吃满了。关掉就好了，CPU 狂飙问题解决。
好像只影响 64 位客户端，我的 32 位客户端都没事。
我在 64 位客户端上看到，它会不停地 spawn 托盘图标，直到 X server 挂掉，所以我是不是该去哪报个 bug？
有意思。我知道 Ubuntu 上最小化到托盘很 clunky，但不知道还 peg CPU。还有人能复现吗？以前 Linux 上这个功能是关掉的，后来觉得有残缺的 UI 也比完全没这功能好。我在想是不是在 Linux 上重新关掉。
英文原文
After it initially tries incorrectly to set itself to the lowest priority, the generate thread only changes its priority again temporarily when it finds a block. When you've found a block, you should want it to hurry up and broadcast it as soon a possible before someone else finds one and makes yours invalid. The generate thread only changes to higher priority for less than a second every few days.
There should be a 0.3.1 release for this soon. There are a few other issues we need to look at fixing in 0.3.1 before making a release.
Quote from: knightmb on July 12, 2010, 10:39:13 PM（https://bitcointalk.org/index.php?topic=299.msg2409#msg2409）On a side note, I've tracked down the other GUI issue.
The "minimize to tray instead of taskbar" is what was eating up all the CPU on my system. After I turned this off, the issue was resolved with Runaway CPU.
This only seems to affect the 64 bit Client, as the 32 bit Clients I have don't seem to be affected by this.
I did notice on the 64 bit Client, what happens is, it spawns multiple "tray" icons until X server finally kills over, so I guess I should submit that as a bug to somewhere?
That's interesting. I know the minimize to tray on Ubuntu is very clunky, but I didn't know it had a CPU peg problem too. Anyone else able to reproduce this problem? We had this feature disabled on Linux before, but then it seemed better to have the imperfect UI than to lose the feature entirely. I'm thinking we should disable it again on Linux.