macOS Catalina 10.15.4 and FAHClient 7.6.9 crash

[donmontalvo]

Thought I'd contribute and install:

Code: Select all

$ /usr/local/bin/FAHClient --version
7.6.9

Crashed a while ago...tried to attach the .crash log file but I don't see a way to...tried to copy/paste the .crash log but got this error:

Your message contains 65051 characters. The maximum number of allowed characters is 60000.

[ajm]

You can edit the log file and delete everything that looks like

Code: Select all

08:04:21:WU02:FS03:0xa7:Completed 455000 out of 500000 steps (91%)

[Joe_H]

If you could post the beginning section of the crash log, that usually is enough to see if there is an identifiable cause. Just the first couple 100 lines should be enough.

[PantherX]

Welcome to the F@H Forum donmontalvo,

Please note that if you need some guidance with posting the log, have a look at this topic: viewtopic.php?f=61&t=26036

[donmontalvo]

Happened a second time, just now, here are the first 100 lines:

---


Process: FAHViewer [1151]
Path: /Applications/Folding@home/FAHViewer.app/Contents/MacOS/FAHViewer
Identifier: org.foldingathome.fahviewer
Version: 7.6.9 (7.6.9)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: FAHViewer [1151]
User ID: 502

Date/Time: 2020-04-21 15:37:29.644 -0400
OS Version: Mac OS X 10.15.4 (19E287)
Report Version: 12
Bridge OS Version: 3.0 (14Y908)
Anonymous UUID: 1FEA2582-3322-9B49-DAC9-4DD160927724


Time Awake Since Boot: 71000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000010374e000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1151]

VM Regions Near 0x10374e000:
MALLOC_LARGE 0000000103736000-000000010374e000 [ 96K] rw-/rwx SM=PRV
-->
MALLOC_LARGE 000000010375e000-000000010377a000 [ 112K] rw-/rwx SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.foldingathome.fahviewer 0x0000000100b9346b FAH::BasicViewer::drawAtom(FAH::Atom const&, cb::Vector<3u, double> const&) + 27
1 org.foldingathome.fahviewer 0x0000000100b944f0 FAH::BasicViewer::drawAtoms(FAH::Protein const&) + 512
2 org.foldingathome.fahviewer 0x0000000100b98574 FAH::BasicViewer::draw(FAH::SimulationInfo const&, FAH::Protein const*, FAH::View const&) + 100
3 org.foldingathome.fahviewer 0x0000000100b820c9 FAH::View::draw() + 153
4 org.foldingathome.fahviewer 0x0000000100b88235 0x100b62000 + 156213
5 com.apple.glut 0x00007fff31aa2b21 -[GLUTView drawRect:] + 93
6 com.apple.glut 0x00007fff31aa288e -[GLUTView handleWorkEvent:] + 3420
7 com.apple.glut 0x00007fff31ab7592 processWindowWorkList + 67
8 com.apple.glut 0x00007fff31ab7530 __glutProcessWorkEvents + 32
9 com.apple.glut 0x00007fff31aab58d -[GLUTApplication run] + 223
10 com.apple.glut 0x00007fff31ab77e7 glutMainLoop + 264
11 org.foldingathome.fahviewer 0x0000000100b630c5 main + 133
12 org.foldingathome.fahviewer 0x0000000100b63034 start + 52

Thread 1:
0 libsystem_kernel.dylib 0x00007fff69101882 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff691c2425 _pthread_cond_wait + 698
2 org.foldingathome.fahviewer 0x0000000100d1d0f4 cb::Condition::timedWait(double) + 84
3 org.foldingathome.fahviewer 0x0000000100d230dd cb::SignalManager::run() + 77
4 org.foldingathome.fahviewer 0x0000000100d3f437 cb::Thread::starter() + 599
5 org.foldingathome.fahviewer 0x0000000100d3ef4a 0x100b62000 + 1953610
6 libsystem_pthread.dylib 0x00007fff691c2109 _pthread_start + 148
7 libsystem_pthread.dylib 0x00007fff691bdb8b thread_start + 15

Thread 2:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff690fedfa mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff690ff170 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff2f0770b5 __CFRunLoopServiceMachPort + 247
3 com.apple.CoreFoundation 0x00007fff2f075b82 __CFRunLoopRun + 1319
4 com.apple.CoreFoundation 0x00007fff2f074ffe CFRunLoopRunSpecific + 462
5 com.apple.AppKit 0x00007fff2c4955b4 _NSEventThread + 132
6 libsystem_pthread.dylib 0x00007fff691c2109 _pthread_start + 148
7 libsystem_pthread.dylib 0x00007fff691bdb8b thread_start + 15

Thread 3:
0 libsystem_pthread.dylib 0x00007fff691bdb68 start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000004 rbx: 0x000000010374e000 rcx: 0x00007fd6c7842a00 rdx: 0x0000000000000940
rdi: 0x000000010416d000 rsi: 0x0000000000000100 rbp: 0x00007ffeef09d160 rsp: 0x00007ffeef09d130
r8: 0x0000000000000001 r9: 0x0000000000000001 r10: 0x0000000000000025 r11: 0x0000000000000010
r12: 0x00007fd6c703a800 r13: 0x0000600002d840c0 r14: 0x00000001064a0000 r15: 0x00007fd6c703a800
rip: 0x0000000100b9346b rfl: 0x0000000000010202 cr2: 0x000000010374e000

Logical CPU: 0
Error Code: 0x00000004 (no mapping for user data read)
Trap Number: 14


Binary Images:
0x100b62000 - 0x1018eefc7 +org.foldingathome.fahviewer (7.6.9 - 7.6.9) <1383A6E4-385A-3848-AFEC-A9297DD36300> /Applications/Folding@home/FAHViewer.app/Contents/MacOS/FAHViewer
0x1044cb000 - 0x104591ff7 com.apple.AMDRadeonX4000GLDriver (3.8.24 - 3.0.8) <C8948AD2-CFF9-31A6-95B9-F2E0A8068EF0> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver
0x1045e7000 - 0x1045ea047 libobjc-trampolines.dylib (787.1) <CCA8AC98-12A2-3984-ACD6-1D77DAD6C0AD> /usr/lib/libobjc-trampolines.dylib
0x107d85000 - 0x107e16eff dyld (750.5) <1F893B81-89A5-3502-8510-95B97B9F730D> /usr/lib/dyld
0x7fff222c3000 - 0x7fff223f0ff8 com.apple.AMDMTLBronzeDriver (3.8.24 - 3.0.8) <15983EE9-C22E-3979-BDB1-51682FFE9442> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
0x7fff223f1000 - 0x7fff22427fff ATIRadeonX4000SCLib.dylib (3.8.24) <FC75895C-348F-3C26-B82F-6E17FFF0E63C> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib
0x7fff2393c000 - 0x7fff242f4ff3 libSC.dylib (3.8.24) <3A787392-149B-3C17-8257-ECB04A04A1B7> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib
0x7fff269f9000 - 0x7fff27a00fff com.apple.driver.AppleIntelKBLGraphicsGLDriver (14.5.22 - 14.0.5) <4C6C15C9-6C8E-3E84-911D-D000FB94794D> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver
0x7fff27a01000 - 0x7fff27e00ff1 com.apple.driver.AppleIntelKBLGraphicsMTLDriver (14.5.22 - 14.0.5) <0BB14CF6-CA95-34B0-B454-0AB95C5D4CF6> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver
0x7fff2ac87000 - 0x7fff2ac87fff com.apple.Accelerate (1.11 - Accelerate 1.11) <8BE0965F-6A6A-35B0-89D0-F0A75835C2CA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff2ac88000 - 0x7fff2ac9efff libCGInterfaces.dylib (524.2) <9092665A-D5C7-3ED8-A7D5-9216B48F8E3E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
0x7fff2ac9f000 - 0x7fff2b2f5fef com.apple.vImage (8.1 - 524.2) <DAE0E5C5-BA70-325D-8B4C-6B821F009CBF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff2b2f6000 - 0x7fff2b55dff7 libBLAS.dylib (1303.60.1) <4E980D6B-4B3A-33D6-B52C-AFC7D120D11A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff2b55e000 - 0x7fff2ba31fef libBNNS.dylib (144.100.2) <C05F9F9D-4498-37BD-9C1C-2F7B920B401D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib

[Joe_H]

So that is a crash of the viewer, not a crash of FAHClient itself. Is FAHClient able to run normally and show up in Activity Monitor?

[donmontalvo]

Ah, wasn't aware, we should be good then:

Code: Select all

# ps -ax -o etime,command -c | grep FAHClient     
01-01:57:52 FAHClient

[bruce]

As Joe_H has said (i'll use different words) FAHClient is essential to donating to science.
FAHViewer is nice to have but nonessential. It can provide nice "eye candy" and maybe give you a better sense of what you're working on, but you can still do as much scientific research without it.

[donmontalvo]

I definitely appreciate the Launch Daemon has a LowPriorityIO key set to true, presumably to keep it from taking up too many resources if the computer owner is working.

However, I'd guess most users would want a way to tell that the process is running, the GUI would be a perfect visual indicator, however it has crashed a bunch of times since I installed it.

Ironically given how CoVID19 has most of us working from home, and the intent of this process is to help crunch numbers to lead to clues and possibly a way to fight it, there's a collision.

I'm a fan, I'm here to contribute, but saying that the GUI doesn't matter isn't a very good response...a better repsonse would be "We know the GUI has issues, but we're stretched thin now."

I get that, anyway I'll remove it for now, happy to test any update that is released to address the GUI issue, and I wish the organization and all contributors the best in fighting CoVID19.

Cheers,
Don

[Joe_H]

FAHControl and Web Control are the GUI, FAHViewer is just a display of the protein system being worked on and is not a GUI. The crash report was passed on, and hopefully will result in a fix eventually.

[SeaJack16]

I've just gotten five panic crashes over 48 hours while running FAH. I'm running MacOS 10.14.6 on a Mac Pro (2010) with 32GB memory and F@H 7.5.1. It's been running without issue for about six weeks. I am also running Norton Security for Mac V8.5.6. Norton gave me a popup saying that a reboot was required to finalize an update. I did but forgot to shut down F@H properly. After the reboot for the Norton update I got the aforementioned panics. I contacted Norton as it was the most logical reason for suddenly getting panics when this machine has gone without crashes for years. They game me the script to completely remove the Norton software with instructions to reinstall. I paused S@H but got distracted and left the system running overnight. There were no crashes overnight so I just left things as is. Norton still installed and S@H paused. It has been several days without any crashes. This really puzzles me as to why does running S@H with the latest Norton cause crashes. I'm attaching the beginning details of one of the crash logs in case anyone can come up with an answer. Note that all crashes involve a failed Xalloc.c call.

Kernel_2020-05-15-093500_SeaJackPro.panic
Anonymous UUID: 08ADD9C7-75FC-B975-8AAA-1E87712F7B9B

Fri May 15 09:35:00 2020

*** Panic Report ***
panic(cpu 2 caller 0xffffff8010edca9d): Kernel trap at 0xffffff80542e1c20, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff80542e1c20, CR3: 0x000000001614d000, CR4: 0x00000000000026e0
RAX: 0xffffff804e9af200, RBX: 0x0000000000000050, RCX: 0x0000000000010001, RDX: 0x0000000000000001
RSP: 0xffffff83a8323d78, RBP: 0xffffff83a8323da0, RSI: 0xffffff8011820780, RDI: 0xffffff80652e6dd0
R8: 0xffffff805313da18, R9: 0x000000000000001f, R10: 0xffffff80116a38f8, R11: 0x0000000000000000
R12: 0x0000000000000005, R13: 0xffffff8066d5f000, R14: 0xffffff8011820780, R15: 0xffffff806d03c4c0
RFL: 0x0000000000010216, RIP: 0xffffff80542e1c20, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0xffffff80542e1c20, Error code: 0x0000000000000011, Fault CPU: 0x2 Kernel NX fault, PL: 0, VF: 2

Backtrace (CPU 2), Frame : Return Address
0xffffff83a8323840 : 0xffffff8010daf58d
0xffffff83a8323890 : 0xffffff8010eeb145
0xffffff83a83238d0 : 0xffffff8010edc87a
0xffffff83a8323940 : 0xffffff8010d5c9d0
0xffffff83a8323960 : 0xffffff8010daefa7
0xffffff83a8323a80 : 0xffffff8010daedf3
0xffffff83a8323af0 : 0xffffff8010edca9d
0xffffff83a8323c60 : 0xffffff8010d5c9d0
0xffffff83a8323c80 : 0xffffff80542e1c20
0xffffff83a8323da0 : 0xffffff80113ce976
0xffffff83a8323dc0 : 0xffffff7f937d5982
0xffffff83a8323de0 : 0xffffff7f937d57aa
0xffffff83a8323e00 : 0xffffff7f937de0d0
0xffffff83a8323e60 : 0xffffff801142b6fd
0xffffff83a8323ea0 : 0xffffff801145570e
0xffffff83a8323ee0 : 0xffffff801142a755
0xffffff83a8323f60 : 0xffffff8011435077
0xffffff83a8323fa0 : 0xffffff8010d5c0ce
Kernel Extensions in backtrace:
com.apple.iokit.IOSurface(255.6.1)[51C0A6EC-149C-3ECE-92E5-ACF817AE1699]@0xffffff7f937d2000->0xffffff7f937f3fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18G4032

Kernel version:
Darwin Kernel Version 18.7.0: Mon Feb 10 21:08:45 PST 2020; root:xnu-4903.278.28~1/RELEASE_X86_64
Kernel UUID: A52CF11D-A733-3E77-832B-D42063739C84
Kernel slide: 0x0000000010a00000
Kernel text base: 0xffffff8010c00000
__HIB text base: 0xffffff8010b00000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 3168471970963470

Thanks,
SeaJack16

[PantherX]

Welcome to the F@H Forum SeaJack16,

Just wondering if you have created an exception for the F@H files in Norton? It is known that some anti-virus products might interfere with folding.

[SeaJack16]

I updated the app from 7.5.1 to 7.6.9. Hopefully no more crashes.

[PantherX]

Please note that V7.6.9 has been superseded by V7.6.13: viewtopic.php?f=24&t=34466

[Joe_H]

@SeaJack16 - I am not seeing anything in that Panic report to indicate a connection to the F@h client software. Is there something else that does indicate that?

Often a kernel panic like this comes from a hardware error. On the software side Norton has a reputation for causing such problems when used on macOS. Their uninstall is not the best at cleaning up after their mess either. Someone who is better than I at reading these may have an idea on what caused the error.