Bet you have multiple processors, or a Pentium HT processor that looks to Boinc like a multi processor system.

Bet you have CP running with other projects too, like SETI. Bet it was fine till you ran out of work for the other projects...

Well when the other projects have no work, CP will try and fill the void. However CP appears to not be able to use multiple processors very well.

I've found on my dual pentitum system that CP alone will lock (make BOINC unresponsive) BOINC when it tries to run the second instance of CP.

I'm able to set my preferance to use only 1 processor and CP run fine by itself. However when I set it to 2 and there is no work from another project CP will try and download more, and lock BOINC.

Hope that helps.

Yes, you are correct, I have a HT Pentium 4. Seems to be working running only CP with 2 CPUs though. I haven't tried just Seti yet.

I have a HT Pentium 4; I'm running only SETI, and it locked up yesterday when it ran out of work units due to the server being shut down.

> Yes, you are correct, I have a HT Pentium 4. Seems to be working running only
> CP with 2 CPUs though. I haven't tried just Seti yet.
>
>

So this means there is a bug, that needs to be fixed, right? Sounds like it's in BOINC not Seti or CP.

Marc

The problem isn't related to any specific project. The GUI "lock up" occurs when BOINC doesn't have work for all available slots. As soon as work becomes available for all slots, the GUI becomes responsive again.

This is definitely a bug in BOINC. Programmatically, it's getting stuck in tight loop. It should be looping in such a fashion as to give up "event slices" (as in VB'd DoEvent) to the OS. This would reduce CPU load and keep the GUI responsive.

I can vouch for the bug being in BOINC. I had to bump CPDN to 200 in order to get it to fill the second slot, then the GUI would finally appear on the taskbar and allow access to its commands. This issue also causes the CLI version to "spin" on one processor, so the bug doesn't reside solely with the GUI executable.

> I can vouch for the bug being in BOINC. I had to bump CPDN to 200 in order to
> get it to fill the second slot, then the GUI would finally appear on the
> taskbar and allow access to its commands. This issue also causes the CLI
> version to "spin" on one processor, so the bug doesn't reside solely with the
> GUI executable.
>
Nope.

Just tried that.

Bumped the resource share to 200. No problem. Set to use 2 processors again it hung.

Unless its this bug is new to BOINC I never had any problems when I was running seti alone. Told it I had two processors and had 100 on the resource share, and it ran fine, even when there was no work. It would just wait.

Will leave it in that state and see if it will free up when Seti pumps out some work units.

I have a dual CPU and have not had any problems along these lines.

http://www.setisynergy.com/stats/boinc-stats.php?id=16457