Loading Profile...
High memory usage
Memory usage is too high for such a simple app. From startup the rescuetime process takes more than 140MB. Sometimes more than Firefox, which by itself is a huge memory hog.
I’m sad
5
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?The Windows client should not be that large. Typically it sits around 20 - 30 mb (which is still a lot larger than we'd like - and we are working on that).
Can you try restarting RescueTime and monitor the memory growth on your system for us? I'd like to know how quickly it is reaching 140mb. With your assistance we can track down why it is growing so large.
If anyone else is seeing similar memory growth, can you also reply with your OS Version and if you are running anything unique or noteworthy?
Thanks for the feedback!
1 person says
this solves the problem
-
Inappropriate?I agree. RescueMe took my machine to its knees when it restarted, almost to the point of not coming back up. Left it over night and it seems better, but was almost a non-starter, even before I got to give it a try.
I’m frustrated
-
Inappropriate?We have had a couple reports that the updater "RescueTimeStart" has caused high cpu usage. I am still trying to track down the cause for that.
If you are seeing high cpu usage, you can kill the RescueTimeStart.exe process and just manually run RescueTime.exe to see if that resolves the issue. -
Inappropriate?Hi Joe. Thanks for the quick reply and the great tool that RescueTime is!
Upon start ProcessExplorer (by sysinternals) shows two related processes: RescueTimeStarter.exe which takes 26.7MB and RescueTime.exe which takes 149.6MB. Both are virtual memory sizes and these values are reached almost immediately. After running it for a while the amount doesn't change much. I'll monitor more closely.
I have Windows XP SP2 nothing unique running here as far as i can tell.
I’m confident
-
Inappropriate?There seems to be something like a memory leak with RescueTimeStart, I'm not sure what's causing it...
But then RTS take indeed almost 100% of the CPU, and guess what, there's even no way to kill the task :o
RescueTime.exe seems to be ok, though ;)
-
Inappropriate?My computer runs for about 20 minutes, and after seeing this topic I thought I should check RescueTime's memory usage on my computer too. RescueTimeStart.exe takes only 2.4MB and RescueTime.exe takes 26.6MB.
P.S.:I got a memory optimization tool, but I disabled it and started RescueTime again. same results, and it doesn't look like its increasing over time.
Edit: Forgot to mention I'm using XP SP2 and about RescueTime(start and the main one) not using almost any CPU power(3% when sending data, 1% when opening or closing the preferences window).
I got a 3GHZ single core CPU. -
Inappropriate?I also have similar problem..I am running on Windows 2003 Server with latest SP and 64 bit platform.. -
Inappropriate?Not only high CPU usage, its taking much more memory than it should have taken.. Just logging the active window shoudnt take more than 500 KB, I think.
I’m very sad by the performance..
-
Inappropriate?Yes way to high. (26,300) i keep popping back here to see if there is a change till then its switched off, and i will just use my google history for on line use.
-
Inappropriate?I've had similar problem - my RescueTime.exe process ate nearly 500MB of RAM. I've discovered that it tries to upload my pending log file of ~478MB size.
And these enormous chunks of logs were generated during the crash of my system... WinXP :) It tried to insert some subset of Log nodes (actually 4 same nodes of <object type="USER_LOGS" id="..."> where id=12..15) unlimited times repeatedly until it totally crashed.
So, it may be that RescueTime.exe eats your memory just for uploading your log files... Check what logs are currently pending to upload (if you know how to do it). And of course, situations like this one should happen very rarely.. I think so. -
Inappropriate?This is happening on Snow Leopard as well. A background process using over 400 megs of memory is crazy!
I’m sad
-
EMPLOYEE
