Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory consumption (dealbreaker) #30

Open
astr0gator opened this issue Nov 5, 2024 · 2 comments
Open

Memory consumption (dealbreaker) #30

astr0gator opened this issue Nov 5, 2024 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@astr0gator
Copy link

Instant google search example works great 🙏
The only caveat is that it generates a process “AlfredExtraPane Web Content” https://www.google.com that takes ~300-400MB of RAM and it stays alive permanently even though I don't use that instant search anymore. With this approach each extra-paned workflow would add up. Any suggestions how on how to terminate it after usage?

@mr-pennyworth
Copy link
Owner

Good point @astr0gator!
Yup, Extra Pane doesn't do any optimizations around the webviews (think of those as embedded safari tabs). This behavior should be fixed!

However, I'm not sure when I'll be able to get around to figuring out how to do the optimization without compromising on the convenience an "always on" pane brings presently. For my personal use, I think this problem went unnoticed because of the high-end macbook provided to me by my employer for my day job 🤣

I'll keep this issue open with a "help wanted" label so that folks can contribute a fix 😇

@mr-pennyworth mr-pennyworth added the help wanted Extra attention is needed label Nov 5, 2024
@astr0gator
Copy link
Author

It's fascinating app. Memory issue is challenging though.
After being testing on my Max with 64GB I can confirm that leaking usage is serious and reach ~1GB. As an avid Ollama/Docker user, I have to stop using alfred-extra-pane since memory is still important for me personally.

Having said that, I agree that for high-end MacBook with 128 GB that you mentioned, it might be less constrained, even though consumption may be actually a bit higher.

Alas, I'm not proficient in Swift, hopefully somebody can help.

@astr0gator astr0gator changed the title Memory consumption Memory consumption (dealbreaker) Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants