Recently active topics in RescueTime tagged with flock

We have released an update to the Windows Data Collector.

You can read about other changes released today at our blog: http://blog.rescuetime.com/2008/02/10...

Bugs Fixed

• Dramatically reduced physical memory footprint for RescueTime.exe. Physical memory should now be around 2 MB (vs 32 MB) during most operations. Physical memory will jump to 11 MB when uploading log files to the RescueTime server, but should drop
  back down to the 2 MB range after the upload completes. Note: Virtual Memory numbers are not affected by this change, which will still report roughly 32 MB, due to the way .Net framework allocates memory.
  
• Additional large file checks to prevent files larger than 1,000K from being sent to the RescueTime.com server.
  
• Removed updater service. This has been causing a number of our users issues and I don't think we are seeing a whole lot of benefit from it. RescueTime will still check for updates upon startup and through the "Check for updates" menu option.

New Features

• URL support for Opera
  
• URL support for Flock

I have been working on a few significant modifications to the Windows Data Collector that I would like to get a handful of Windows users involved with.

If you are interested in helping out, read on.

Windows Data Collector - 0.9.9

Fixes:

* Dramatically reduced physical memory footprint for RescueTime.exe. Physical memory should now be around 2 MB (vs 32 MB) during most operations. Physical memory will jump to 11 MB when uploading log files to the RescueTime server, but should drop back down to the 2 MB range after the upload completes. Note, Virtual Memory numbers are not affected by this change, which will still report roughly 32 MB, mostly due to the way .Net framework allocates memory.

* Additional large file checks to prevent files larger than 1,000K from being sent to the RescueTime.com server.

* Removed updater service. This has been causing a number of our users issues and I don't think we are seeing a whole lot of benefit from it. RescueTime will still check for updates upon startup and through the "Check for updates" menu option.

New Features:

* URL support for Opera

* URL support for Flock

Specific Testing I'm asking for:

* Feedback on the update process. To remove the updater service, there are some scripted commands that run during the update. These commands should remove the RescueTimeStart process owned by the SYSTEM user (which can be seen in the Task Manager). If you still see a RescueTimeStart process running after completing the update let me know. Also, please report any errors or unexpected behavior during the update process.

* Memory utilization and performance impacts after the install. The aggressive memory reclamation that I'm doing does take some processing. On the test systems that I've run the new data collector on I have not noticed any performance degradation and CPU utilization is typically < 1%.

* Opera and Flock URL support feedback. To get current URL's from Opera, I had to deploy DDE libraries which is why you will see a couple of new files in your installation directory.

How to get the update:

* In the directory where RescueTime is installed (default c:\Program Files\RescueTime), there is a file named UpdateServer.ini. Change the contents of that ini file from "www.rescuetime.com/updates" to "dev.rescuetime.com/updates"
* Select "Check for updates" from the RescueTime menu or restart RescueTime with the RescueTimeStart.exe and you should be informed that there are new updates available.

Respond to this forum post with any feedback you have.

Thank you!