Author Topic: [Solved] Memory leak with avast pre-release build 5.0.661  (Read 18508 times)

0 Members and 1 Guest are viewing this topic.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: BSOD with CTM and avast pre-release build 5.0.661
« Reply #30 on: August 30, 2010, 11:00:10 PM »
This will be fixed by another beta refresh, probably tomorrow.

Sorry for the trouble.
This is the "memory leak"?
The best things in life are free.

Hard_ROCKER

  • Guest
Re: BSOD with CTM and avast pre-release build 5.0.661
« Reply #31 on: August 31, 2010, 07:23:58 AM »
Hey guys. Today i woke up, sat behind the pc and there it was, the infamous running out of memory pop-up message. Hope the new beta refresh will be out soon...

Offline Rednose

  • Pirate Party Member
  • Avast √úberevangelist
  • Massive Poster
  • *****
  • Posts: 3737
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: BSOD with CTM and avast pre-release build 5.0.661
« Reply #32 on: August 31, 2010, 07:29:49 AM »
Yep, the 661 BETA release has probably a memory leak. I suspected it, and mentioned it yesterday to Logos in the chat after which he posted here too.

Greetz, Red.
OS: Win 10 / iOS 15 / Debian 11 / Tails 4
Real Time: Avast Premium Security
On Demand: Malwarebytes
VPN: NordVPN ( NordLynx ) with CyberSec

Hermite15

  • Guest
Re: BSOD with CTM and avast pre-release build 5.0.661
« Reply #33 on: August 31, 2010, 10:39:03 AM »
yeah Red thanks for telling me about it because I didn't suspect Avast ;) (thought it was Chrome)

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11660
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: BSOD with CTM and avast pre-release build 5.0.661
« Reply #34 on: August 31, 2010, 02:59:38 PM »
Please update to the latest build (668) - should have the problem fixed.

Thanks
vlk
If at first you don't succeed, then skydiving's not for you.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: BSOD with CTM and avast pre-release build 5.0.661
« Reply #35 on: August 31, 2010, 03:35:24 PM »
I've thought it was CTM ;D

Please update to the latest build (668) - should have the problem fixed.
Thanks :)
The best things in life are free.

Online DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 87304
  • No support PMs thanks
Re: Memory leak with avast pre-release build 5.0.661
« Reply #36 on: August 31, 2010, 05:39:39 PM »
@ Tech
Perhaps you need to change the Original Post topic since 5.0.668 resolves this memory leak or add [Resolved] at the end of it.

You changed the title in the second post (BSOD with CTM and avast pre-release build 5.0.661) but the original title is still shown in the listings, so if that is still the case you need to change the original posts title.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.12.6044 (build 22.12.7758.768) UI 1.0.741/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: Memory leak with avast pre-release build 5.0.661
« Reply #37 on: August 31, 2010, 05:57:53 PM »
Perhaps you need to change the Original Post topic since 5.0.668 resolves this memory leak or add [Resolved] at the end of it.
I'll do when I can say that for sure...
Up time now 2h 7min and seems ok.
The best things in life are free.

Hermite15

  • Guest
Re: Memory leak with avast pre-release build 5.0.661
« Reply #38 on: August 31, 2010, 06:07:17 PM »
yes same here, for me it's considered solved ;)

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: Memory leak with avast pre-release build 5.0.661
« Reply #39 on: August 31, 2010, 07:13:23 PM »
Solved.
Now let's try the sandbox and see if the BSOD is also solved with CTM.
The best things in life are free.

Hard_ROCKER

  • Guest
Re: [Solved] Memory leak with avast pre-release build 5.0.661
« Reply #40 on: August 31, 2010, 07:50:48 PM »
Everything back to normal over here aswell. :)