Jump to content

pbparker

Members
  • Posts

    12
  • Joined

  • Last visited

Reputation

0 Neutral
  1. The idle memory leak appears to be fixed for me with the latest beta. However, I was able to push the memory from 49M to 58M with 9 runs of the updatedb.exe program you gave me, so not sure if that leak is fixed yet, but the more critical one appears resolved.
  2. Well, I guess I won't be able to test until I get home tonight. Tried reenabling it all on my home computer via remote desktop and I get Error Code 2. So I uninstalled, restarted, cleaned, restarted, installed, registered and clicked start protection and now I get error code 1073 and am unable to start the protection.
  3. I'm going to start the testing now, but I'm curious why we're testing the update process only when my install is set to update at 1:00 AM and I have turned off automatic updates - and with all that turned off the memory rises anyways. Seems to me the memory increases are related to something other than the update procedure, but again I'm speculating without knowing if there's something else going on behind the scenes.
  4. Yeah.. I've had to fully disable everything with the app for now until this problem is resolved.
  5. Not for me, memory climbs when both are disabled. As I posted in my last message memory was at 162M when both were disabled. I just checked my computer (it's at home) remotely and memory is up to 167M now. Both protections are still disabled and there were no updates or scans taking place nor any activity on the computer.
  6. FYI, the memory climbs when IP protection is disabled as well as protection itself disabled. I clocked it from 12:48 CST to 2:17 CST, the memory went from 155M to 162M. I'd be willing to create some debug info for ya, will PM ya.
  7. I've done all that too, and the folder under Program Files was not there before I did the reinstall. I had run the cleaner and rebooted multiple times. Now, this morning I checked the computer after not having been on it all night, and the process is up to 143 megs.
  8. Nope, didn't resolve the problem. Started at around 50 megs after restart and now a few hours later it's up to 81 megs. This is after HOURS not days even.
  9. I woke up this morning and the memory had gone to 144 megs. Now applying the exclusions to my antivirus, will let you know how it goes.
  10. Yeah, I just uninstalled, ran the cleaner and reinstalled and am having the same memory balloon issues. This has only started happening recently too, never did this before. Installed initially it consumed around 50 megs mem/vm and then after a manual update, went to 60 megs. Now after surfing the web for a few hours, they're both at 100 megs. Running Windows XP SP3 with Pentium D/3.00 Ghz with 2 Gb of memory.
  11. Ahh, very good, that would resolve my issues. Thanks much.
  12. Hosted by GoDaddy it would appear. Yeah... the range of IP's around it have had issues it looks like (http://hosts-file.net/?s=208.109.78.134&view=matches) but if that's the reason MBAM is going to block and it isn't going to distinguish between a single bad IP and a whole range/provider - then it needs some ability to permanently to turn off IP protection. I do like the IP protection idea, but it would also be better if other than giving a balloon just indicating it's blocked, that there was some way of looking into more information. In addition, perhaps instead of disabling IP protection fully, there was an exclusion list that can be created for sites of our own choosing.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.