[Bug]: Version 2.2.0 (4033) is crashing with sigsegv

[DougHockin]

Before submitting your bug report, please confirm you have completed the following steps

• [X] Searched the issue is not already listed in the Issue List (I've searched it)
• [X] Searched in the Quicksilver Users' Group for questions relating to tech support.
• [X] Downloaded the latest version of Quicksilver for your system and confirmed the issue still persists.

Bug description

Quicksilver crashes with SIGSEGV

Steps to reproduce

1. Start Quicksilver and use it for a while
2. It crashes

Expected behavior

Shouldn't crash, but:

May 25 20:10:50 Dougs-MacBook-Pro com.apple.xpc.launchd[1] (application.com.blacktree.Quicksilver.8628724025.8628724030[18737]): Service exited due to SIGSEGV | sent by exc handler[18737]

MacOS Version

macOS 11

Quicksilver Version

2.2.0 (4033)

Relevant Plugins

No response

Crash Logs or Spindump

No crash log available, just a message in system.log: May 25 20:10:50 Dougs-MacBook-Pro com.apple.xpc.launchd[1] (application.com.blacktree.Quicksilver.8628724025.8628724030[18737]): Service exited due to SIGSEGV | sent by exc handler[18737]

Screenshots

No response

Additional info

No response

[fraserw]

Seeing the same behavior. OSX 11.6.5.

[pjrobertson]

Please try looking in Console.app here for a crash log, and then uploading it:

[DougHockin]

I've looked. There are no crash reports. The SIGSEGV is happening repeatedly, a dozen times a day. My system has no User Reports (folder?) showing in the console, only Crash, Spin, Log, Diagnostic, Analytics and system.log. Is it possible some system configuration is (by default?) preventing it from creating crash reports?

[nevioth]

attaching txt of report crash.txt Edit: pardon, this is happening now with 4034 as well as it did with 4033 for me

[DougHockin]

On both old and new hardware architectures. Looks like corruption of malloced memory pool.

[DougHockin]

Duplicate of bug report #2878.

[n8henrie]

I'll go ahead and close as duplicate as the other issue precedes this one, and the conversation seems to be consolidating there, and @pjrobertson has submitted a potential fix -- thank you @DougHockin and @nevioth, please let us know if this needs to be re-opened.