SwiftBar: Memory corruption crashes every few days

Describe the bug I have been seeing SwiftBar crashes (either SIGSEGV or SIGABRT) due to memory corruption.

I haven’t been able to detect a consistent pattern with the crashes. They seem to happen every couple of days, typically after I’ve put my machine to sleep. They seem to happen when my machine does a macOS “power nap” wakeup, though I am not certain on that.

I’m attaching 3 crash reports to the bug. Two are segfaults (SIGSEGV) and one is a SIGABRT triggered by malloc() detecting heap corruption.

Environment:

  • macOS version: 12.3.1 on Intel
  • SwiftBar version: 1.4.3, installed from the homebrew cask

Additional Context:

I have 3 scripts running:

  • A bash script that runs every 5 seconds
  • A Go program that runs every 5 seconds
  • A Go program that runs every 30 seconds

I do run Bartender. I have not (yet) tried running without it, though I previously ran earlier 1.4.x versions under it without issue.

I’ve attached the crash reports generated my macOS below. GitHub did not like the original ips extension, so I appended .txt to them. They are JSON files, however, but can be rendered more prettily by Console.app.

SwiftBar-2022-05-05-191332.ips.txt SwiftBar-2022-05-06-165801.ips.txt SwiftBar-2022-05-11-205124.ips.txt

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (8 by maintainers)

Commits related to this issue

Most upvoted comments

@melonamin No issues here. I feel comfortable with it, and I think you can probably close this issue now. I’ll reopen it or file another if I start seeing the issue again. I’m sorry we couldn’t precisely identify it!

Just as an FYI, I’ve been running this build for about a week now without any crashes. I’ll update if and when I see one.

@joeshaw I’ve added crash reportiing, please try running this build SwiftBar.1.4.4b448.zip

@gimbo It crashes and the items leave the menubar.

An older version (1.4.1 iirc) had an issue where items stopped updating, but that was fixed and I haven’t had any problems with updating since.