-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Big memory consumption #118
Comments
There seems to be a problem with apps that have an invalid signature. When such an app is started and the Lulu Alert pops up, the app remains in LuLu's memory. |
LuLu/launchDaemon/launchDaemon/KextListener.m Lines 503 to 504 in 9e8016c
I guess the binary is not being released from memory. |
I believe I'm running into a similar issue. My lulu process held onto 4GB of memory. |
I'm glad that somebody had raised this issue. I often find myself having to kill Lulu because of its excessive resource demand. Looking forward to a solution! |
+1 |
+1.2 million I realise that this is a Gift Horse and that we shouldn't peer too deeply into its mouth but, it really would be nice if this memory issue can be acknowledged. Is a "fix" being considered? |
Umm... is there a valid reason for this serious issue to remain ignored? On the other hand, if it's not really an "issue" but just something which only a scant few of us experience because of coincidental stupidity, could we please have some guidance to help extricate us from this quagmire? I'd like to experience the promise of LuLu so that I can sing its praises! Currently, I'm just bemoaning its unworkable sucking-the-life-out-of-my-memory tendency. |
Sorry for the delay on this 😔
Sorry again for the delay. |
Thanks I'll look into this logic more! As the code is compiled with ARC (automatic reference counting) in theory, that process object should be automatically freed when the method returns, or once the process exits 🤔 But maybe something else is holding on to it, so it's not being relinquished... |
I have put an autorelease pool block around it and had no memory issues in the last couple of weeks. |
The autorelease pool block looks interesting.. I've been having loads of issues with LuLu consuming stupid amounts of RAM and I believe that is triggered either by docker or minikube, which also points to a possible issue with hyperkit as it's common to both of these services/apps. These seem to be the common triggers I've come to notice, but then again, I run both of these pretty regularly so it could be just a coincidence that LuLu hogs memory while these services are running. I have a couple screenshots available with how much mem LuLu is using (and the memory pressure) and right after being killed, but I think the issue is clear enough that we don't need more screenshots. |
An "autorelease pool block" looks impressive! It also seems like something that must be done "under the hood" and hence, it's well beyond my capabilities. Nevertheless, thanks for looking into this problem and planning to move it along to a resolution. |
Any updates when fix will be released? |
+1 |
1. Added autorelease pool (hopefully to address Big memory consumption #118) 2. Improved validation of XPC connection acceptence to ensure only LuLu components can talk to daemon's XPC interface (mahalo Wojciech Reguła @_r3ggi!)
@objective-see - Any possibility of creating the release with this fix? |
I gave up long ago. This software, although appealing, is utterly unusable on my system without the fix that was promised long ago. I had no choice but to remove it. I appreciate that this is FOSS produced and shared by the developer with no obligations whatsoever to anybody who uses it but, come on, why don't you follow through? |
@atulagrwl, yups: The binary was also released on the product's page: https://objective-see.com/products/lulu.html If you're still seeing memory issues, please lmk :) |
Woo hoo; thanks! It's loading now... |
@objective-see - thanks a lot. |
Alas, I've had to delete LuLu from my machine. Its demand for 45% of my CPU resources, thus killing my productivity, is too much to bear. Adios, ciao... |
Now I have a much more serious problem. Although I removed the lulu sub-directory from the Applications directory, the thing is still alive. It's a freakin' zombie which simply doesn't want to die! Please , how do I drive a stake through it's resource-gobbling heart to remove it once and for all? |
You can simply download the LuLu installer again, run it and click "Uninstall" See: https://objective-see.com/products/lulu.html for more details |
This seems to be still an issue, or again an issue. For me (M1) it still consumes too much memory. If it is hashing related, can we have a checkbox to disable hashing at all? I mean it is only relevant if you try to compare it with VirusTotal which is the minority of cases. |
I thought that I commented that it was no longer an issue for me. I've been running lulu again for almost a year without any of the earlier issues. The problem for me, if I recall correctly, was another program running in the background and impeding lulus ability to work properly. Unfortunately, I've forgotten the specific program! It could have been an Übersicht module but, I'm not sure. |
Seems to either reset inbetween or I did restart LuLu. Yesterday it was at 300mb and 600mb at another point. Today it was at 50mb (not open) and 110mb with open rules-window. Don't know, maybe it was a temporary hiccup. And I also experience the slow loading times from time to time. Maybe these two are related. |
Hi,
Mac OS 10.14.2 (18C54)
The text was updated successfully, but these errors were encountered: