Author Topic: [SOLVED]memory leak in aswmon2.sys?  (Read 48640 times)

0 Members and 1 Guest are viewing this topic.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: memory leak in aswmon2.sys?
« Reply #45 on: July 02, 2012, 03:09:24 AM »
I've got a memory leak today in one of my XP systems...
The best things in life are free.

Offline Herrminator

  • Jr. Member
  • **
  • Posts: 26
Re: memory leak in aswmon2.sys?
« Reply #46 on: July 02, 2012, 10:04:33 AM »
The P2P usage is an assumption not a certainty

I don't use any P2P programs, but there's several batch-backup jobs running in the night.
Some of them do rename whole directory trees, all of them do a lot of copying...

J.Stalin

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #47 on: July 02, 2012, 10:36:03 AM »
I think it is time to admit that the new version was released without proper testing.
There are several serious bugs. Just look at the topics. Memory leak makes XP useless. There are problems with Outlook, and many users have problems with definition updating. I would find it appropriate if Avast withdraw this version so the users don't get it by automatic update.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89029
  • No support PMs thanks
Re: memory leak in aswmon2.sys?
« Reply #48 on: July 02, 2012, 02:16:44 PM »
The P2P usage is an assumption not a certainty

I don't use any P2P programs, but there's several batch-backup jobs running in the night.
Some of them do rename whole directory trees, all of them do a lot of copying...

As I said the P2P suggestion was a bit of a SWAG (Scientific Wild Assed Guess), but yes your batch backup jobs could result in a lot of rename operations. I certainly don't have anything like that going on on my XP system. Other than my weekly drive imaging software backup, but that shouldn't cause much in the way of rename operations as the backup creates one image file of each partition on my primary hard disk to my secondary drive.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Chim

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 1151
Re: memory leak in aswmon2.sys?
« Reply #49 on: July 02, 2012, 03:56:58 PM »
My computer locked up again yesterday evening for the 3rd time in Sunday alone.
Again, I got one of those messages of "Insufficient System Resources" and had to crawl into just being able to reboot.

So, I'm now back down to 7.0.1426.
Dell Optiplex 780 / Core 2 Duo E8400 3.00 GHz / 4 Gig RAM / Windows XP Pro 32-Bit SP3 / Panda Dome  Free 18.07.00 / MBAM / SAS / NetZero Dial Up / Maxthon MX5 5.2.5.4000

Hillbilly

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #50 on: July 02, 2012, 05:31:13 PM »
Hi There! I also had a massive problem with a memory leak too. I only have a little eMachines EL-1600 that has only 1 GB ram, a 1.6GHz Intel Atom 230 and up to 256MB ram is shared and used for graphics. It's a gutless little "net top". However, with version 1426 I had no problems whatsoever. At the moment I've switched back to AVG Free 2012 which is OK, but that' about it - it's OK. Better than MS SE, but nowhere near as powerful or as good as Avast. I has the same dissapearing fonts and "out of memory" messages that the others have described. This little machine is running Win XP SP3.  I'll keep checking back to see when this memory leak issue is resolved.

One thing I really miss is the real time protection that Avast has, as well as the boot-time scan. AVG has neither in their free version.  Please email me as soon as this issue has been resolved. The reason I updated to version 7.0.1451 is because 7.0.1426 stated that the program as "out of date".  Thanks.

Offline mchain

  • Avast Evangelist
  • Ultra Poster
  • ***
  • Posts: 5604
  • Spartan Warrior
Re: memory leak in aswmon2.sys?
« Reply #51 on: July 02, 2012, 08:05:04 PM »
(SWAG), that's good.   :D

Just trying to do some thinking outside the box, as some programs installed or tasks run that Avast! may not be able to handle correctly, like Outlook, Chrome, memory leaks, emergency updater functions, etc.

Software configuration of everyone's system is always different, some better, some worse.  Nothing is standardized, that's for sure.
Windows 10 Home 64-bit 22H2 Avast Premier Security version 24.1.6099 (build 24.1.88821.762)  UI version 1.0.797
 UI version 1.0.788.  Windows 11 Home 23H2 - Windows 11 Pro 23H2 Avast Premier Security version 24.2.6105 (build 24.1.8918.827) UI version 1.0.801

RichardN

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #52 on: July 02, 2012, 08:09:21 PM »
I think I'm in the same boat as you guys. I'm running XP SP3, I upgraded Avast to 7.0.1451 the other day, and my system has been having problems.

After a while I start to lose text on the screen - where text should be it appears blank. Then if I try to call up Task Manager using ctrl-alt-delete the screen goes blue except for a Windows XP box giving me a few options such as shutting down or logging off.  I get error messages, though I can't always read what they say.

I was worrying that this was a virus, but now I think it may be a memory leak caused by my Avast update. Can anyone tell me if what I have described sounds familiar?

J.Stalin

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #53 on: July 02, 2012, 08:21:28 PM »
Don't waste time on it, it doesn't work on XP. Install the previous version.

Nawach

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #54 on: July 02, 2012, 08:54:07 PM »
I think it is time to admit that the new version was released without proper testing.
There are several serious bugs. Just look at the topics. Memory leak makes XP useless. There are problems with Outlook, and many users have problems with definition updating. I would find it appropriate if Avast withdraw this version so the users don't get it by automatic update.

I do agree...

I'm far to be an expert, but I can't help but wonder whether Windows 8 could be the "culprit" for all this mess? I mean, it's supposed to be so different compared to XP and 7 (or is it just it's GUI that's different?)

Offline mchain

  • Avast Evangelist
  • Ultra Poster
  • ***
  • Posts: 5604
  • Spartan Warrior
Re: memory leak in aswmon2.sys?
« Reply #55 on: July 02, 2012, 09:44:50 PM »
I'm far to be an expert, but I can't help but wonder whether Windows 8 could be the "culprit" for all this mess? I mean, it's supposed to be so different compared to XP and 7 (or is it just it's GUI that's different?)
Windows 8 is a major update, Win 7 not so much, Vista was a major update, XP was minor in comparison, Win 2000 major, so...   Historically this is the release pattern Microsoft has followed.

XP is getting long in the tooth, as the basic os really has not changed since release in 2000, support for SP has ceased, and as time progresses, Microsoft will support it less and less.  Microsoft will not support this os after April 8. 2014.

For example, support for SATA hard drives was never included in SP3.

http://www.microsoft.com/en-us/windows/endofsupport.aspx

This means all security updates will end, and as the cutoff date approaches, less and less work will be done to update it.

So yes, Win 8 is the focus right now, and XP is looking at diminishing returns.  Where Avast! devs come in, is the work necessary to work with an older os and also work with the newest.  Twelve years is a long time to support any os, yet Avast! is still supporting Win 2000.  So they are choosing to support quite a few os's from Microsoft.

EDIT:  As this is a little off-topic, I will leave this alone and say no more.
« Last Edit: July 02, 2012, 09:49:11 PM by mchain »
Windows 10 Home 64-bit 22H2 Avast Premier Security version 24.1.6099 (build 24.1.88821.762)  UI version 1.0.797
 UI version 1.0.788.  Windows 11 Home 23H2 - Windows 11 Pro 23H2 Avast Premier Security version 24.2.6105 (build 24.1.8918.827) UI version 1.0.801

J.Stalin

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #56 on: July 02, 2012, 10:06:42 PM »
If you want to advertise any particular Microsoft product, I suggest you find another place to do it. This topic is started by a few posters who did an excellent research.
There is still no fix from Avast who released a product that don't work on XP, which in april this year was installed on 25,86 of the worlds pc's.
Please keep this topic on track so a quick fix can be made, and the users do not start new posts about the same bug, because the posts end up with non-relevant stuff.

Offline Gopher John

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2098
Re: memory leak in aswmon2.sys?
« Reply #57 on: July 02, 2012, 11:53:55 PM »
There is still no fix from Avast who released a product that don't work on XP, which in april this year was installed on 25,86 of the worlds pc's.

Avast Free 7.0.1451 works well on my WinXP Pro SP3.  It just doesn't work for you, and some others. ::)
AMD A6-5350M APU with Radeon HD Graphics, 8.0GB RAM, Win7 Pro SP1 64bit, IE11
i7-3610QM 2.3GHZ, 8.0GB Ram,  Nvidia GeForce GT 630M 2GB, Win7 Pro SP1 64bit, IE 11
Common to both: Avast Premium Security 19.7.2388, WinPatrol Plus, SpywareBlaster 5.5, Opera 12.18, Firefox 68.0.2, MBam Free, CCleaner

RichardN

  • Guest
Re: memory leak in aswmon2.sys?
« Reply #58 on: July 03, 2012, 12:48:12 AM »
I uninstalled 7.0.1451 and tried to re-install 6.0.1367 but ran into a problem: Setup Selfextract popped up a dialogue box informing me I was trying to use an old version of avast!setup, and that it would download and use latest setup from the internet instead. It didn't give me any other options. Since I was offline at this point it couldn't do that, but refused to go any further. So I was forced to go  back to 7.0.1451 to have virus protection, buggy as it is.

What did I do wrong?

Offline Herrminator

  • Jr. Member
  • **
  • Posts: 26
Re: memory leak in aswmon2.sys?
« Reply #59 on: July 03, 2012, 10:08:56 AM »
It just doesn't work for you, and some others. ::)

Well, following this thread and the main release thread, it's not just only some  :-\