回复：64 位比特币（Linux 客户端）的 CPU 占用失控
原始发布页
打开来源页面查看 1 个交叉存档
最初错误地尝试把自身设为最低优先级之后，生成线程只会在找到区块时再次临时改变优先级。当你找到一个区块时，你应该希望它赶紧尽快广播出去，免得别人也找到一个区块，让你的区块失效。生成线程每隔几天才会把优先级调高不到一秒钟。
应该很快就会为此发布 0.3.1。在发布之前，我们还需要看看能否修复 0.3.1 中的其他几个问题。
引用 knightmb 于 2010 年 7 月 12 日 10:39:13 PM 的发言
顺便说一句，我已经找到了另一个 GUI 问题。
“最小化到托盘而不是任务栏”正是耗尽我系统全部 CPU 的原因。关闭它之后，CPU 占用失控的问题就解决了。
这似乎只影响 64 位客户端，因为我的那些 32 位客户端好像不受这个问题影响。
我确实注意到，64 位客户端会不断生成多个“托盘”图标，直到 X server 最终崩溃，所以我想我应该去什么地方把它作为 bug 提交？(疑惑)
这很有意思。我知道 Ubuntu 上的最小化到托盘功能非常笨拙，但不知道它还会造成 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
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? (Huh)
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.