Crashing with Problem Event Name: CLR20r3

Glyphex

New Member
Code:
Description
Faulting Application Path:    C:\Program Files (x86)\Adguard\Adguard.exe

Problem signature
Problem Event Name:    CLR20r3
Problem Signature 01:    Adguard.exe
Problem Signature 02:    7.8.3779.0
Problem Signature 03:    61baf73b
Problem Signature 04:    Adguard.Ipc
Problem Signature 05:    7.8.3779.0
Problem Signature 06:    61baf72b
Problem Signature 07:    16a
Problem Signature 08:    122
Problem Signature 09:    System.OutOfMemoryException
OS Version:    10.0.19044.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    c407
Additional Information 2:    c407e8568793094cb1bf9eea560fdc80
Additional Information 3:    815a
Additional Information 4:    815aa410889b84f33450e9d8c3c470e8

Extra information about the problem
Bucket ID:    1212a8ecc1d00be9c586caba39c8302c (1551150022857863212)
This is with the latest client update: 7.8.
The application is constantly crashing, making it pointless to even run it. I just want to get to the bottom of this, it's either my computer or an application problem. Considering this is a 2 year old computer with 16GB RAM; I am concerned about the OOM issue.
 

SakuKen

New Member
Any update on this? I've been having the same issue where Adguard will periodically exit with an OutOfMemoryException.

Application: Adguard.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at Adguard.Ipc.Client.BasicApplicationApiClient`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Disconnect(Boolean, Boolean)
at Adguard.Ipc.Client.BasicApplicationApiClient`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ListenToServerEvents()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

This may be the same issue tracked here:

The machine itself is not out of memory.
 

Glyphex

New Member
Reformatted my PC. Issue is still present. (Reformatted out of personal want, not specifically for AdGuard) I would appreciate an update from the team if possible. I purchased the license because I generally love this software!
 

CeeTee

New Member
Similar - 7.8 crashing all the time, requiring shutting down the service and then restarting AG to get it working again - quite frustrating. No problems prior to the auto-update to 7.8

Note: I suspect this is happening when filters are automatically updated.
 
Last edited:

SakuKen

New Member
This is getting pretty old. Now it's not just the main program but the backing service that crashes:

Application: AdguardSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
at System.Threading.Timer.Change(Int32, Int32)
at B1sqSFDQKeQaN9Fl4SJ.IE2KdSrFS(System.Object, Int32, Int32, B1sqSFDQKeQaN9Fl4SJ)
at Adguard.Service.Filtering.NetworkFilteringService.PerformSafebrowsingUpdate()
at Adguard.Service.Filtering.NetworkFilteringService.ty3kqaeok9(System.Object)
at System.Threading.TimerQueueTimer.CallCallbackInContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
at System.Threading.TimerQueue.AppDomainTimerCallback(Int32)

Of course the main app can't behave either:

Application: Adguard.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
at System.Drawing.SafeNativeMethods+Gdip.GdiplusStartup(IntPtr ByRef, StartupInput ByRef, StartupOutput ByRef)
at System.Drawing.SafeNativeMethods+Gdip.Initialize()
at System.Drawing.SafeNativeMethods+Gdip..cctor()

Exception Info: System.TypeInitializationException
at System.Drawing.SafeNativeMethods+Gdip.GdipCreateFontFromLogfontW(System.Runtime.InteropServices.HandleRef, System.Object, IntPtr ByRef)
at System.Drawing.Font.FromLogFont(System.Object, IntPtr)
at System.Drawing.Font.FromHfont(IntPtr)
at System.Drawing.SystemFonts.get_DefaultFont()
at System.Windows.Forms.Control.get_DefaultFont()
at System.Windows.Forms.Control.get_Font()
at System.Windows.Forms.Control.get_FontHeight()
at System.Windows.Forms.TextBoxBase.get_PreferredHeight()
at System.Windows.Forms.TextBoxBase.get_DefaultSize()
at System.Windows.Forms.Control..ctor(Boolean)
at System.Windows.Forms.TextBoxBase..ctor()
at System.Windows.Forms.TextBox..ctor()
at System.Windows.Forms.ThreadExceptionDialog..ctor(System.Exception)
at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)
at System.Windows.Forms.NotifyIcon+NotifyIconNativeWindow.OnThreadException(System.Exception)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
 

SakuKen

New Member
For everyone still getting periodic crashes of their Adguard service, set it to automatically restart.

Windows Run > services.msc > Right click "Adguard Service" > Select Properties > Select Recovery Tab
Set all of First, Second, Subsequent failure dropdowns to "Restart the Service"
Set "Restart service after" to 0 minutes to get it to immediately restart


If your Adguard application is crashing you'll have to find a way to have it automatically restart. I wrote a short program in .net to restart it on the Process.Exited event. There are probably existing solutions out there. A quick online search leads to https://www.raymond.cc/blog/keep-application-running-by-automatically-rerun-when-closed/

Hopefully this tides everyone over until better defensive coding practices can be put in place.
 

Attachments

Top