search

objective-see / BlockBlock

BlockBlock provides continual protection by monitoring persistence locations.
GNU General Public License v3.0
626 stars 39 forks source link

BlockBlock stuck not responding after upgrade to 11.3 Beta 6 #25

Open jguerin opened 3 years ago

jguerin commented 3 years ago

I noticed that BlockBlock Helper would get stuck in a Not Responding state after upgrading to the latest Big Sur beta.

Reinstalling from the website fixed the issue.

Attaching samples in case they help diagnose the issue. Sample of BlockBlock Helper.txt Spindump of BlockBlock Helper.txt

tjluoma commented 3 years ago

I noticed the same thing tonight with macOS version 11.4 (20F5046g) (aka "11.4 beta 1")

Sample files:

BlockBlock-Sample-Files-2021-04-30.zip

I also tried running it via lldb:

$ lldb /Applications/BlockBlock\ Helper.app/Contents/MacOS/BlockBlock\ Helper
(lldb) target create "/Applications/BlockBlock Helper.app/Contents/MacOS/BlockBlock Helper"
Current executable set to '/Applications/BlockBlock Helper.app/Contents/MacOS/BlockBlock Helper' (arm64).
(lldb) run
error: process exited with status -1 (attach failed (Not allowed to attach to process.  Look in the console messages (Console.app), near the debugserver entries when the attached failed.  The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.))
(lldb)

After reinstalling, I realized that the process /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock had not been running previously when the "Helper" was trying to run, so I wonder if it was not able to "attach" because root wasn't running /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock ?

(Oh, this is running on an m1 MacBook Air, if it matters.)