Memory leak in Intouch v9.5 P3 if using 2ndary source (IO Failover)

[wildswing]

FYI...I've been getting a lot of wwHeap errors lately. After discussing with my vender tech support I found out that there's a memory leak in v9.5 if you enable the secondary source for an access name aka IO failover. WW has a hot fix. I haven't received it yet.

[jmalter]

This is news to me. Do you have any more information on the problem? I have a number of WW systems with that configuration on a job site in China with WW newbies starting them up. They have not reported any problem. We staged the system for several weeks but did not have any continuous operation of the application.

[wildswing]

All I can tell you is I saw the memory usage of view.exe climb by about 40 Mb per day from an initial 20 - 25 Mb. Once they hit the wwHeap limit, view would crash. I've patched a couple of my nodes and it seems to have fixed the leak. FYI, I had raised the memory usage limit for wwHeap from the default 256 to 512 Mb a few weeks before on the advice of my venders tech support guys but that just meant it took longer before view crashed. The patch is available from WW tech support but you have to sign one of their release waivers to get it.

[wildswing]

Update: I've applied the patch to all of our Intouch nodes. It's a replacement of view.exe. All seem to be working fine and are not gobbling up memory like before. However, on restart [of OS and Intouch] I had one node give me a heap error. It started fine after another restart. I've forwarded the relevant info to tech support and am awaiting their reply.