Opened 17 years ago

Closed 15 years ago

#282 closed Defect (fixed)

BM can crash during multiple up/download

Reported by: Contact Owned by: davea
Priority: Minor Milestone: Undetermined
Component: Client - Daemon Version:
Keywords: Cc:

Description

If there are many files up/downloading, boinc.exe uses very high CPU% and BOINC Manager is slow to respond (selecting tab or item, moving slider etc.) BM can easily crash during this situation.

Attachments (1)

crash.png (91.5 KB) - added by Contact 17 years ago.
BOINC Manager not responding

Download all attachments as: .zip

Change History (7)

Changed 17 years ago by Contact

Attachment: crash.png added

BOINC Manager not responding

comment:1 Changed 17 years ago by Nicolas

There's actually two different problems there:

  • BOINC core client uses very high CPU% and doesn't respond to manager requests if there are too many file transfers in queue
  • BOINC Manager hangs and doesn't respond to keyboard/mouse if the core client doesn't reply; which could be caused by many reasons, including a hanged client, or a network problem (if the manager is connected to a remote client).

Technical details for the second problem: this is because the manager uses blocking I/O to communicate with the client.

comment:2 Changed 17 years ago by MikeMarsUK

David has marked the second issue as 'probably fixed in 5.9.12, reopen if not'

http://boinc.berkeley.edu/trac/ticket/113

Do we know what version is being referred to in this ticket (282?)

comment:3 Changed 17 years ago by MikeMarsUK

And there was the duplicate I created (http://boinc.berkeley.edu/trac/ticket/171) of course.

comment:4 in reply to:  2 Changed 17 years ago by Contact

Replying to MikeMarsUK:

David has marked the second issue as 'probably fixed in 5.9.12, reopen if not'

http://boinc.berkeley.edu/trac/ticket/113

Do we know what version is being referred to in this ticket (282?)

Version 5.10.6 according to crash.png, but have seen similar behavior with other versions when too many up/downloads waiting.

comment:5 Changed 17 years ago by Nicolas

#286 marked as duplicate of this bug. However, note that the description on #286 seems to be more complete than the one here.

comment:6 Changed 15 years ago by romw

Resolution: fixed
Status: newclosed

This should now be fixed in the latest 6.6 clients.

Note: See TracTickets for help on using tickets.