Re: Runaway CPU usage for 64bit BitCoin (Linux Client)

I did a forum search, didn’t see this mentioned by anyone yet.

I have 5 Bit Coin clients, some running Windows Bit Coin, others running Linux Bit Coin.

I only have one 64 bit Linux system, but when I run Bit Coin, after about 10 minutes, the CPU usage runs away and brings the system to a stall unless I kill the Bit Coin application.

Now I have 2 other computers running a 32 bit Linux Bit Coin client and they work just fine, no runaway CPU.

I’ve tried running the 32 bit Bit Coin on the 64 bit Linux system, but the same thing still happens. My 64 bit Linux system has a dual-core processor, and even when I choose the “use only 1 processor” option, after a while Bit Coin ends up using both CPU to the 100% max that it can.

Is this a bug that only affects 64 bit Linux users at the moment?

Using the latest version 0.3.0 from the front page of the website.

System OS: Linux Mandriva 2010.0 (64 bit)
Processor – Intel Dual-Core 3.06 CPU

Feedback or advice welcome.  🙂

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, 22:39:13
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.

17,246 total views, 70 views today