Loading Profile...
EventBox hogs memory
Over time EventBox uses more and more "real memory." It starts off OK, around 60MB, but over time it comes close to or exceeds Firefox as the single biggest memory hog on my computer. Only quitting and relaunching EventBox seems to fix the problem. I saw on Twitter that the developer is aware of this problem and that it is "not a memory leak" but some other problem which will be fixed by version 1.0. Still, I thought it should be posted here so other users can vote on this bug and share their own experiences.
I’m disappointed
18
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I'm guessing this has to do with WebKit. EventBox and WebKit almost perfectly parallel eachothers' memory usages on my machine. Both are currently hovering around 400mb. -
Inappropriate?It's not actually related to WebKit. Technically, it's not a bug - it was a design tradeoff. It's an inherent property of the way we use Core Animation - trading speed for memory. We have some ideas on how to optimize it but this is going to happen once we're happy with the feature set offered. -
Inappropriate?How long will that take? I was quick to purchase EventBox but I rarely use it now because of the serious hit it puts on my system. I really like the app and would prefer to be able to use it more often.
I’m concerned
1 Comment
Add a comment
This solves the problem
-
We don't really know exactly how long it would be but I can tell you that it's not an easy 1-2 weeks fix. There are two things I can suggest:
- If EventBox is unusable for you, then it's better to get a refund (email us). One thing we don't want is users buying our software and not being able to use it.
- If you try to keep the number of events in the current selected container to about (200-300), memory usage shouldn't be that high -
Inappropriate?I'm not interested in getting a refund. I really like EventBox and registered it a lot quicker than I usually do with shareware. I'm just hoping to see improvements in its memory usage.
-
Inappropriate?I downloaded the app from Macheist today.. I also face the same issue... I love the app.... but too much memory hog
I’m sad
1 Comment Add a comment
This solves the problem
-
Do you use it for Google Reader / Feeds?
-
Inappropriate?Yes. I use it for Google Reader. Also for Flickr and Twitter.1 Comment Add a comment
This solves the problem
-
How many feeds do you approximately have (and have many posts)?
-
Inappropriate?I have 19 feeds and 421 unread posts as of now1 Comment Add a comment
This solves the problem
-
That should use something in the range of 100-150MB (estimate). Is that right?
-
Inappropriate?334mbs used, after a few days running, with 577 unread items in Google Reader. A lot of feeds, not sure how many. A lot. 950 unread items total.
I’m amused
2 Comments Add a comment
This solves the problem
-
I would actually expect it to use a lot more than 335 for this setup. I completely agree with everyone that this usage is too much and I apologize for that. We will do our best to fix the situation but it's not a simple problem to resolve.
-
Yeah, it seems to cap at ~400 for me, and then go back down a bit when I haven't really been using it. Not sure why.
-
Inappropriate?Nope... It goes upto 400-450 MB if I leave it up for an hour or two
-
Inappropriate?I left EventBox running overnight, and this morning it was using nearly 2GB of memory - eek!
About 100 subscriptions in Google reader, but only 70 or 80 unread items across all the services.4 Comments Add a comment
This solves the problem
-
Do you remember if you had GR selected in the main window? Also, do you have more than 1.5k posts?
-
I'm not 100%sure, but I think I just had the Unread items selected. Number of posts - was 70 or 80 unread as I mentioned, and maybe a couple of hundred that had been read.
-
This comment was removed on 03/30/09.
see the change log -
This comment was removed on 03/30/09.
see the change log -
Inappropriate?Using the MacHeist 'free' version and have had Eventbox using up to 2GB of 'real ram' - slowing down my computer to a crawl. Such a shame cos it's a lovely app - but unusable.
I’m frustrated
-
Inappropriate?I've been using EventBox for a few days now and have noticed the same problem. I would much rather have efficient memory usage than any additional features at this point. Memory should always be a primary concern and not secondary to features.
http://farm4.static.flickr.com/3473/3...
Please address this or unfortunately I'll have to move on. As much as I love the interface, it consistently uses more than 5 times the memory other clients use.
I’m frustrated.
-
Inappropriate?I'm a paid user, and I love EventBox, but I'm having the same issue. If I leave EB open overnight, when I come back it's almost always using over a GB of memory. If I go mark everything as read, it frees up a bit of space, but it never again dips below the 1 GB mark. I've been just quitting when I leave and restarting when I come back, but I'm hoping that it will be a bit less memory-intensive when it comes out of Beta.
Screencap of Activity Monitor:
I’m ambivalent
-
Inappropriate?I've been prototyping the new architecture for the main view which is less memory intensive. We've done some internal tests and memory usage went down from 400MB to about 40MB constant. Obviously, this is all preliminary and just a prototype architecture but I'm quite confident that we will be able to get this to production quality. Solving the mem usage problem is our next task and the reason it's taking longer is because we're rewriting a big and complex portion of the app in order to accommodate the changes.
-
Inappropriate?Milen, that's all I want to hear. Maybe EventBox should have had these things fixed before release, maybe if I hadn't rushed to purchase it so quickly I wouldn't be impatient in waiting for fixes. In the end, it's a great idea that I hope ends up becoming great software. What works now is awesome. The rest will come. I hope.
I’m confident
1 Comment Add a comment
This solves the problem
-
Looking at the past, we didn't realize it was going to be problem because during internal testing everything was fine. Unfortunately, we were so wrong but we will fix it.
-
Inappropriate?I also have this memory problem, but I'm hoping to see the problem resolved soon.
As for now a worried licensed user with great hope for a future fix (not too far away I hope).
Besides that Eventbox is really nice
I’m undecided
