Endnote X1 has huge memory leak when skinned with WB6
from
Stardock Forums
Hi,
As per the title, I wanted to report to Stardock that Endnote X1 (a common and popular bibliographic software solutin in academia) seems to suffer a huge memory leak when skinned by WB6 under XP sp2. Doesn't seem to be a skin specific issue, although I first noticed it using Diamond XP.
Specifically, Endnote is ok on startup, but clicking on any reference in any reference list will start a gradual memory suck, which if left unattended will crash Endnote after about 15 minutes or so (at about 1 GB for the process). Everytime the Endnote window is minimized to the taskbar, memory is purged, but the suck will start over again, next time you click a ref. Interestingly, the process is also paused (but memory is not returned) if a drop down menu is opened in Endnote.
I can't find any WB per application setting that resolves this, but setting it to just ignore Endnote does avoid the issue.
If there's anything else worth trying, please let me know. Otherwise, maybe ISI and Stardock can figure out who's software is at issue here, and come out with a fix? Note that you can download a free demo of Endnote at www.endnote.com, for compatibility testing.
Thanks much,
J...
As per the title, I wanted to report to Stardock that Endnote X1 (a common and popular bibliographic software solutin in academia) seems to suffer a huge memory leak when skinned by WB6 under XP sp2. Doesn't seem to be a skin specific issue, although I first noticed it using Diamond XP.
Specifically, Endnote is ok on startup, but clicking on any reference in any reference list will start a gradual memory suck, which if left unattended will crash Endnote after about 15 minutes or so (at about 1 GB for the process). Everytime the Endnote window is minimized to the taskbar, memory is purged, but the suck will start over again, next time you click a ref. Interestingly, the process is also paused (but memory is not returned) if a drop down menu is opened in Endnote.
I can't find any WB per application setting that resolves this, but setting it to just ignore Endnote does avoid the issue.
If there's anything else worth trying, please let me know. Otherwise, maybe ISI and Stardock can figure out who's software is at issue here, and come out with a fix? Note that you can download a free demo of Endnote at www.endnote.com, for compatibility testing.
Thanks much,
J...