Ticket #398 (new Defect)

Opened 11 months ago

Last modified 11 months ago

Boinc 5.10.20 crash - account manager?

Reported by: tiker Assigned to: davea
Priority: Minor Milestone: Undetermined
Component: Client - Daemon Version:
Keywords: crash memory-corruption Cc:

Description

Here's the history: I had setup a new install of Windows XP with SP2 on an Intel Core 2 Dual 6600 (2.4ghz) system. I installed client 5.10.20 to run as a service, no interaction with the desktop. I attached the client to BAM and then from the client connected to WCG. The system processes for a while. A couple days later the boinc client had unloaded itself / crashed.

Looking at the logs it seems that BAM told the client to detach from WCG which the client did but then continues to try and cruch a work unit which is probably what lead to the crash.

I've attached the two log files which had data in them. I didn't have any debug options enabled, sorry.

Attachments

stderrdae.txt (13.7 kB) - added by tiker on 09/07/07 13:51:15.
stdoutdae.txt (67.6 kB) - added by tiker on 09/07/07 13:51:36.

Change History

09/07/07 13:51:15 changed by tiker

  • attachment stderrdae.txt added.

09/07/07 13:51:36 changed by tiker

  • attachment stdoutdae.txt added.

09/07/07 14:29:11 changed by Ageless

  • priority changed from Undetermined to Minor.

When using BAM (or any other account manager) attach to projects through BAM only. Or if you truly must attach to a project with the client, make sure you disabled it in BAM. You'd best post this first on the BOINCStats/BAM forums.

I'll leave component at nothing (and thus the ticket not assigned to anyone) for now.

09/07/07 14:40:35 changed by Nicolas

  • keywords set to crash memory-corruption.
  • owner set to davea.
  • component changed from Undetermined to Client - Daemon.

In any case, this shouldn't have crashed the client. Considering the workunit names shown later, it looks like memory corruption. Nothing very useful on the stacktrace though, since obviously it shows the moment of the crash and not the moment where the memory corruption happened.

It would be useful if somebody can reproduce this.

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.