[Bug]: Safari plugin #3052
Description
Before submitting your bug report, please confirm you have completed the following steps
- Searched the issue is not already listed in the Issue List (I've searched it)
- Searched in the Quicksilver Users' Group for questions relating to tech support.
- Downloaded the latest version of Quicksilver for your system and confirmed the issue still persists.
Bug description
Lots of commentary on the old email list, the text of which essentially says that huge amounts of memory is being used which appears to be down to the Safari plugin. Having removed the Safari from my system (macOS Sequoia 15.4.1 on M3 iMac and QS 2.5.1 I can concur.
The full transcript is below under 'Additional info.'
Steps to reproduce
Expected behavior
No tangible increase in memory usage
MacOS Version
15.4.1
Quicksilver Version
2.5.1
Relevant Plugins
Safari 2.5.0
Crash Logs or Spindump
No response
Screenshots
No response
Additional info
Safari Plugin is the culprit. Dropped from 20+GB to 80MB of memory after deactivating the plugin and restarting Quicksilver.
On May 10, 2025, at 1:29 AM, Laurie Caday [email protected] wrote:
So I followed the directions linked to my last response and about plugins possibly causing large amounts of data activity and this is what Activity Monitor report on Quicksilver and indeed this is the cause of the large amounts of memory used. It also has not crashed in a couple of days either! Thank you so much.
On Sunday, May 4, 2025 at 3:54:48 AM UTC-7 Tim Lawson wrote:
Add them back in one at a time to find out. Please let us know here.
On 4 May 2025, at 11:34, Jim Syler <[email protected]> wrote:
That seems to have worked, though you have to quit and restart QS in order to see a change after disabling a plugin.
Wonder which plugin it was?
On Sunday, April 27, 2025 at 1:07:41 PM UTC-5 Rob Winchester wrote:
Laurie - Try turning off all of the QS plugins and see if it improves? That was what worked for me. Then I reenabled those I really thought I needed and have had no problem.
On Apr 27, 2025 at 2:05:41 PM, Laurie Caday [email protected] wrote:
These two windows show what happens after only a few minutes of Quicksilvers use.
These two Activity Monitor screenshot show what is really happening with Quicksilver....... so no wonder it randomly quits. Not a single crash reports either.
On Sunday, April 27, 2025 at 11:00:51 AM UTC-7 Laurie Caday wrote:
Wrong attachments
Here are the correct ones:
On Sunday, April 27, 2025 at 10:57:29 AM UTC-7 Laurie Caday wrote:
I thought I'd include this info on Quicksilver's issues. Yes at what time Quicksilver randomly quits.....there is no Console reports on the crash or quitting. But running Activity Monitor here is some real time info. I have included screenshots for several as to Quicksilver's behavior. It is gobbling massive amounts of resources.
I am running Mac OS Sequoia on an M1 MacBook Pro.
On Wednesday, April 23, 2025 at 1:09:35 AM UTC-7 Laurie Caday wrote:
I am having similar usage patterns. with no crash reports at all either.........
What do you suggest?
On Thursday, April 17, 2025 at 2:23:53 PM UTC-7 Jim Syler wrote:
And now it’s quitting after a while, possibly because it’s using many GB of RAM. I Guess I’ll downgrade to 1.4.3.
On Thursday, April 17, 2025 at 3:47:16 AM UTC-5 Jim Syler wrote:
I just updated to 1.5.1 (on Catalina) and I'm seeing insane resource usages, like 95% CPU and 32 GB RAM. It's acting like malware. Is this happening to anyone else? What's going on?