Win7 - Anyone else using?

[JonFo]

I upgraded my HTPC/automation server to Windows7 a month or two ago, and had to do a few things to get 3.30.02 running.

First, was to set the app as "run as administrator", as it wants to write to the Program files directories.

Second, based on some threads here about hanging tasks on multi-processor CPU's, I decided to launch it with CPU core affinity settings in the Desktop shortcut used to launch the app:
C:\Windows\System32\cmd.exe /C "start /affinity 2 HouseBotServer.exe"

The above line forces the app to run on the second core in my dual-core server.

However, I've noted that I have a pretty serious memory leak with the server just running idle. It loses about 8K per second [edit: after a few minutes, it's up to 76K/sec]

After a day, its racked up over a gig of used memory, and gets real slow. Obviously something's not right.

I think I have all tracing off and all tasks are stopped. No clients talking to it either.

Any input as to what to try next?

Anyone else running 3.30 on Win7?

[JonFo]

Doh!

I forgot that early on, I had selected 'Run this program in compatibility mode' and set it for WinXP SP3 compatibility. (or the installer set it that way).

Once I unchecked that, and just let it run 'as-is', no more memory leak

It's been running along for ten minutes now at roughly the same memory level.

[ScottBot]

That's interesting. I guess Microsoft needed to replicate their poor memory management problems in the compatibility mode also.

I've been running my main home system on Windows 7 since it came out. It's been running great for me.

You will see a slight memory increase over a period of time initially. This is due to log messages getting buffered (error logs and system logs). These logs are capped, so after a point, the memory consumption should level out.

[JonFo]

Thanks Scott, yes, it looks like they replicated the 'bugs' as well in 'compatibility' mode

After a day, it has only gone up 400K, and is not really changing.

I've been using it heavily, lot's of scripts, theme edits, testing, etc. so the footprint is indeed staying small even in the face of high usage.