[Bug]: Frequent freezes, and app stuck on running checks

[ezra-preno]

What happened?

Also claims cloud dashboard is not receiving reports.

Version

1.21.0 - Build 6943 - app-live-stream
macOS - 26.2, M4 Pro

Relevant log output

[zupo]

Hey @ezra-preno, thanks for the bug report! I have a question: do you use a third-party firewall like LittleSnitch or similar? It seems like something is blocking Pareto Desktop from reporting to Pareto Cloud.

[dz0ny]

@ezra-preno could you also send the sampled report to support@paretosecurity.com? From the screenshot, it shows 14 hangs, and those should be included in the sampled report.

[zupo]

There is a pre-release with fixes available on https://github.com/ParetoSecurity/pareto-mac/releases/download/1.21.3/ParetoSecurity.dmg.

We've been testing it internally for the last few days and didn't see any hangs. Could you give it a try?

[ezra-preno]

@ezra-preno could you also send the sampled report to support@paretosecurity.com? From the screenshot, it shows 14 hangs, and those should be included in the sampled report.

Sent.

[ezra-preno]

Hey @ezra-preno, thanks for the bug report! I have a question: do you use a third-party firewall like LittleSnitch or similar? It seems like something is blocking Pareto Desktop from reporting to Pareto Cloud.

I use LuLu for the firewall, I got a new link from my admin and it started working again. LuLu didnt prompt me for a new connection though.

[ezra-preno]

Hangs also may happen after waking from sleep for the weekend.

[dz0ny]

Claude found this from sample:

The sample trace shows the app is hung on the main thread executing an NSAppleScript call that sends an Apple Event to System Events and never gets a reply.

Call chain (lines 26-75):

1. A timer fires on the main thread (__NSFireTimer)
2. Pareto Security code calls runOSA(appleScript:) (in Utils.swift:149)
3. NSAppleScript.executeAndReturnError() sends an Apple Event to System Events
4. It blocks in mach_msg2_trap waiting for a response that never comes

Line 23 confirms the cascade effect:
Dispatch Thread Soft Limit: 70 reached in 2161 of 2165 samples -- too many dispatch threads blocked in synchronous operations

The blocked main thread causes dispatch threads to pile up (70 threads exhausted).

The problematic checks

Two checks call runOSA() synchronously on the main thread:

• AutologinCheck (Autologin.swift:28) — tell application "System Events" to tell security preferences to get automatic login
• RequirePasswordToUnlock (PasswordtoUnlock.swift:28) — tell application "System Events" to tell security preferences to get require password to
  unlock

Why it hangs

System Events can become unresponsive (busy, sandboxed restriction, or waiting on another Apple Event). Since runOSA() is called synchronously on the
main thread with no timeout, the entire app freezes indefinitely.

[dz0ny]

@ezra-preno Can you check if you have Pareto Security enabled in > System Preferences > Privacy & Security > Automation.

[ezra-preno]

@ezra-preno Can you check if you have Pareto Security enabled in > System Preferences > Privacy & Security > Automation.

Yes, it is.