search

BOINC / boinc

Open-source software for volunteer computing and grid computing.
https://boinc.berkeley.edu
GNU Lesser General Public License v3.0
2.03k stars 449 forks source link

[Manager] When preferences window remains open, Manager crashes #4950

Open Vulpine05 opened 2 years ago

Vulpine05 commented 2 years ago

Describe the bug If you open the computing preferences in Manager and leave it open, Manager will eventually crash. This seems to happen only in simple view, not advanced. The client appears to continue to run.

Steps To Reproduce

  1. Launch BOINC, switch to simple view for the manager.
  2. Options-> Computing preferences...
  3. No need to edit any settings, just leave this window alone. Wait some time (hours?) and the Manager window will disappear.

Expected behavior Manager should remain open.

System Information

Additional context I have not been able to witness when Manager crashes. I suspect it may happen when a task completes, but I have no reason to assume that. I lock Windows when I walk away, so I notice the Manager has crashed when I log back in hours later.

AenBleidd commented 2 years ago

@Vulpine05, please activate postmortem debugger as it's said in this tutorial ( https://www.windowscentral.com/how-use-procdump-create-dump-files-windows-10 ), wait for next crash and send me a crash dump. I'll check what exactly happened.

AenBleidd commented 2 years ago

Potentially the same issue #4330 ?

Vulpine05 commented 2 years ago

@Vulpine05, please activate postmortem debugger as it's said in this tutorial ( https://www.windowscentral.com/how-use-procdump-create-dump-files-windows-10 ), wait for next crash and send me a crash dump. I'll check what exactly happened.

Okay, I have tried at least half a dozen times to get a dump log, and nothing has been generated.

Command Prompt is opened as an administrator and after unzipping I type procdump -ma -i C:\dumps

Manager crashes (system tray icon disappears, too), but no log is generated in the dumps folder (yes, the folder is created, too). What am I missing?

AenBleidd commented 2 years ago

@Vulpine05, have you used procdump or procdump64? The first one is x86, the second one is x64. Not sure exactly, but could be a reason why 32-bit debugger doesn't catch 64-bit applications failures. Also, please check Windows Registry (regedit.exe) path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug and that the value Debugger is similar to this:

"C:\SRC\procdump\procdump64.exe" -accepteula -ma -j "C:\SRC\Dumps" %ld %ld %p

Both paths, of course, should be yours and could be different from mine

Vulpine05 commented 2 years ago

@AenBleidd, I had been using procdump, and I just tried today with procdump64, with the same results. Registry has the same executable with flags as you listed above (relative to my path).

However, I see in the registry it is -j, whereas the instructions have a -i, if that means anything.