Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
AppGuard bypassed (old version)
Message
<blockquote data-quote="askmark" data-source="post: 542006" data-attributes="member: 55081"><p>No memory dumps have been requested, although I have offered to send them. Dan has improved the freeze issue by identifying a memory leak, which occurred due to too many alerts appearing while the user was away and not being there to answer them. These alerts were causing VS to consume and not release a significant amount of heap memory. The memory problem has definitely been resolved as I've since measured VS's mem use using perfmon for a week and it never went above 100MB, despite forcing it to scan some really large files (some over 600MB). </p><p></p><p>What's left is a freeze issue that's not memory related. Personally, I think Dan needs to request system information from everyone who is experiencing the problem to see if they share a common hardware or software component.</p></blockquote><p></p>
[QUOTE="askmark, post: 542006, member: 55081"] No memory dumps have been requested, although I have offered to send them. Dan has improved the freeze issue by identifying a memory leak, which occurred due to too many alerts appearing while the user was away and not being there to answer them. These alerts were causing VS to consume and not release a significant amount of heap memory. The memory problem has definitely been resolved as I've since measured VS's mem use using perfmon for a week and it never went above 100MB, despite forcing it to scan some really large files (some over 600MB). What's left is a freeze issue that's not memory related. Personally, I think Dan needs to request system information from everyone who is experiencing the problem to see if they share a common hardware or software component. [/QUOTE]
Insert quotes…
Verification
Post reply
Top