Has anyone else noticed a serious problem with sp4.1 after a few configuration switches etc, coming to it's knees and being so slow it has to be closed and reloaded? I didnt have this issue with sp4.0 but sp4.1 is unusable due to this issue.
Nothing noticeable here either.
No problems either but something is different with 32-bit version. After opening an assembly, memory usage jumps up as before but after minimizing SW window down, almost all memory is released. And after activating SW again, memory usage is not as big as it was with the first opening.
Settings: Resolve everything always and memory usage optimized for programs.
This is not same with 64-bit. There system takes memory needed but it will not release it as with 32 bit.
Not sure if this came with 2009SP4.1 or before.
What are your system specs, Luke?
Depending on what OS you are using, Task Manager may not be a reliable way to gauge memory usage.
I got these (pics) right after installing sp4.1, but only once. and I really didn't have anything special going on. Never got these before..well, at least I don't remember. Maybe it's related?
I get the same errors as Markku does but I'm still on SP4.0. SWX 2009 has been super slow since the day of install when working on large assemblies. Mating seems to take forever.
Dell Precision T3400Intel Core2 ExtremeCPU X9650 @ 3.00GHz15GB of RamNVIDIA Quadro FX 4600MS Windows XP Pro x64 SP2SWX 2009 SP4.0
I've had the same message Markku. Only has happened maybe a couple times, but never before the recent update.
I'm also running 09 SP4.0
I should mention I am using the 64 bit Vista version. Also just had this memory issue cause a corruption of the file late yesterday. Lost another half day work. Uninstalling and reinstalling for the second time and staying with SP0
Problem solved. SP0 did the trick. No more loss of performance over time. No excessive save or rebuild times. No more corruption of file.
Something in SP4.1 did not agree with my system.
Luke, could you provide the process you used.
I have an identical problem that you described and it's unbearable, not to mention a time killer.
I tried to install 4.0, but it automatically installs 4.1
Dell Precision M6300
Intel 2 Duo
T7500 @ 2.20GHz
2.19 GHz, 3.50 GB RAM
Windows XP-pro 32bit Version 2002 SP3
I read the previous post that mentioned OUTLOOK and problems. So, I noticed that indeed if I run SW 4.1 and do not open a session of Outlook, it runs like a champ. As soon as I start Outlook, even if I close it, the brakes come on in SW. So, reboot the computer and don't start Outlook and it again runs like a hungry Beaver on a pine tree.
I have edited my registry per the instructions and keeping my fingers crossed. I'll report back with my findings after a few start/stop sessions
my problem isn't due to outlook. I am running Vista 64 bit, so my registry settings dont match up with what has been posted as a fix for XP. My issue appears to be due to the program not managing memory properly with a 64 bit system.
Retrieving data ...