High RAM consumption during filter updates

[cjom]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question

Operating system type

Linux, OpenWrt

CPU architecture

AMD64

Installation

GitHub releases or script from README

Setup

On a router, DHCP is handled by the router

AdGuard Home version

v0.108.0-a.466+9f7a582d

Description

What did you do?

Installed AGH on router and set filters to update every 24h.
Filters are saved in /opt (not RAM) trying to use less RAM, also logs are reduced to spare RAM.

Expected result

While using around 250MB of RAM for AdGuardHome only, the router usually still has more than 70 MB of free RAM.
AdGuardHome should manage the available RAM to update filters without crashing.

Actual result

"top" command shows that AGH is reserving 932 MB when there are 406 MB usable (229% of VSZ).
When comes the time to update filters, AGH tries to allocate 932 MB and then it invokes oom-killer on itself due to lack of free RAM.

Screenshots (if applicable)

[   61.700658] AdGuardHome invoked oom-killer: gfp_mask=0x1100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), order=0, oom_score_adj=0
[   61.700723] CPU: 0 PID: 5074 Comm: AdGuardHome Not tainted 5.15.98 #0
[   61.710610] Hardware name: Xiaomi AX3600 (DT)
[   61.717031] Call trace:
[   61.721365]  dump_backtrace+0x0/0x180
[   61.723627]  show_stack+0x18/0x30
[   61.727445]  dump_stack_lvl+0x6c/0x88
[   61.730743]  dump_stack+0x18/0x34
[   61.734389]  dump_header+0x44/0x180
[   61.737687]  oom_kill_process+0x1e0/0x1e4
[   61.740987]  out_of_memory+0x1c8/0x2fc
[   61.745153]  __alloc_pages_slowpath.constprop.0+0x82c/0xa44
[   61.748803]  __alloc_pages+0x210/0x25c
[   61.754268]  alloc_zeroed_user_highpage_movable+0x24/0x30
[   61.758091]  wp_page_copy+0x378/0x88c
[   61.763556]  do_wp_page+0xa0/0x434
[   61.767200]  __handle_mm_fault+0x69c/0xa70
[   61.770500]  handle_mm_fault+0x148/0x1f0
[   61.774580]  do_page_fault+0x14c/0x3e0
[   61.778660]  do_mem_abort+0x44/0xb0
[   61.782218]  el0_da+0x24/0x60
[   61.785603]  el0t_64_sync_handler+0xac/0x114
[   61.788731]  el0t_64_sync+0x184/0x188
[   61.793138] Mem-Info:
[   61.796632] active_anon:67573 inactive_anon:42 isolated_anon:0
[   61.796632]  active_file:170 inactive_file:28 isolated_file:0
[   61.796632]  unevictable:0 dirty:0 writeback:0
[   61.796632]  slab_reclaimable:1701 slab_unreclaimable:9055
[   61.796632]  mapped:25 shmem:20 pagetables:362 bounce:0
[   61.796632]  kernel_misc_reclaimable:0
[   61.796632]  free:4878 free_pcp:146 free_cma:0
[   61.811694] Node 0 active_anon:270292kB inactive_anon:168kB active_file:680kB inactive_file:112kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:100kB dirty:0kB writeback:0kB shmem:80kB writeback_tmp:0kB kernel_stack:2160kB pagetables:1448kB all_unreclaimable? yes
[   61.835988] DMA free:19512kB min:16384kB low:20480kB high:24576kB reserved_highatomic:0KB active_anon:270276kB inactive_anon:168kB active_file:72kB inactive_file:472kB unevictable:0kB writepending:0kB present:524288kB managed:416628kB mlocked:0kB bounce:0kB free_pcp:584kB local_pcp:256kB free_cma:0kB
[   61.862645] lowmem_reserve[]: 0 0 0 0
[   61.884844] DMA: 647*4kB (UME) 421*8kB (UME) 265*16kB (UME) 66*32kB (UME) 19*64kB (UME) 8*128kB (UM) 6*256kB (UME) 2*512kB (UM) 2*1024kB (M) 0*2048kB 0*4096kB = 19156kB
[   61.888502] 215 total pagecache pages
[   61.903598] 0 pages in swap cache
[   61.907176] Swap cache stats: add 0, delete 0, find 0/0
[   61.910458] Free swap  = 0kB
[   61.915474] Total swap = 0kB
[   61.918628] 131072 pages RAM
[   61.921475] 0 pages HighMem/MovableOnly
[   61.924330] 26915 pages reserved
[   61.927889] Tasks state (memory values in pages):
[   61.931372] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
[   61.936003] [    732]    81   732      344       30    32768        0             0 ubusd
[   61.944523] [    733]     0   733      226        9    32768        0             0 askfirst
[   61.952762] [    768]     0   768      263       16    28672        0             0 urngd
[   61.961248] [   1285]   514  1285      332       21    32768        0             0 logd
[   61.969307] [   1345]     0  1345      941      131    32768        0             0 rpcd
[   61.977477] [   1802]     0  1802      690       26    40960        0             0 hostapd
[   61.985547] [   1803]     0  1803      690       26    40960        0             0 wpa_supplicant
[   61.993620] [   1817]   101  1817      780       52    40960        0             0 hostapd
[   62.002646] [   1818]   101  1818      760       32    40960        0             0 wpa_supplicant
[   62.010895] [   1867]     0  1867      515       52    32768        0             0 netifd
[   62.019913] [   2148]     0  2148      405       29    32768        0             0 odhcpd
[   62.028190] [   2207]     0  2207      328       13    28672        0             0 crond
[   62.036421] [   2273]     0  2273      688       35    32768        0             0 uhttpd
[   62.044691] [   3439]     0  3439      276       16    32768        0             0 dropbear
[   62.052853] [   3835]     0  3835      690       28    36864        0             0 dnsmasq
[   62.061444] [   3845]   453  3845     1179       97    40960        0             0 dnsmasq
[   62.069628] [   4645]     0  4645   255774    66712   692224        0             0 AdGuardHome
[   62.077846] [   4791]     0  4791      341       24    28672        0             0 sh
[   62.086503] [   4915]     0  4915      690       28    40960        0             0 ntpd
[   62.094493] [   4937]   123  4937      327       14    32768        0             0 ntpd
[   62.102745] [   5095]     0  5095      341       28    28672        0             0 sh
[   62.110844] [   5096]     0  5096      327       13    32768        0             0 logger
[   62.118545] [   5113]     0  5113      327        9    28672        0             0 sleep
[   62.126806] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=AdGuardHome,pid=4645,uid=0
[   62.135075] Out of memory: Killed process 4645 (AdGuardHome) total-vm:1023096kB, anon-rss:266848kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:676kB oom_score_adj:0
[   95.885732] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
[   95.885960] br-lan: port 5(phy1-ap0) entered blocking state

  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 7479     1 root     S     932m 229%   0% /usr/bin/AdGuardHome -c /etc/adguardhome.yaml -w /opt/AdGuardHome -s run --no-check-update

Additional information

Right now it's running edge build, but it also happens with beta build and with v107.

The problem seems to be AGH trying to blindly allocate 930 MB of RAM when it should instead check how much free RAM there is (more than 70 MB) and manage to update the filters with it.
I suppose 70 MB should be plenty RAM to update any lists.

[fixsssator]

Confirm. Have the same problem. With all functions disabled as DHCP, optimistic caching and all disabled filters i got killed process and "out of memory" too.
Use adguard v107 for AX3600

[ainar-g]

Hello.

Filters are saved in /opt (not RAM) trying to use less RAM, also logs are reduced to spare RAM.

Just to clarify, are you using the file paths instead of URIs in your filtering settings?

Also, how large are the rule files exactly?

[cjom]

TL;DR
AGH allocates a lot of RAM when settings are changed, like "Filter update interval" or even deactivating a filter list.
Even with 80 MB of free RAM it crashes with "Out of memory" error.

Just to clarify, are you using the file paths instead of URIs in your filtering settings?

I am using the URI, all from AdGuard:
https://adguardteam.github.io/HostlistsRegistry/assets/filter_*.txt

What I meant to say is the working folder is /opt and not /var or /tmp, trying to save some RAM.

Also, how large are the rule files exactly?

Getting details for this question, I found more data that I hope is useful.

For some reason, AGH allocates a lot of memory when changing settings, like "Filter update interval" (even if disabling). Also, simply disabling lists can make it crash too, because it seems to also allocate a lot of memory when a list is disabled...

• ALL LISTS DISABLED = 151~164 MB of free RAM, no crashes changing settings.

Free RAM values are a loose reference, as I noticed they float a lot as I change settings in AGH for testing.

• 1 list (The NoTracking blocklist = 9540026 bytes, 452712 rules) and free RAM drops to 83~86 MB
  Just clicking "update filters" made the free RAM drop to 51 MB

With only this list (9.5 MB) any changes to settings, like "filter update interval", makes AGH crash...

• 1 list (OISD Blocklist Full = 6681559 bytes, 282087 rules) and free RAM drops to 130~135 MB
  Just clicking "update filters" made the free RAM drop to 110 MB

No crash when changing settings...

• 16 lists (8.2 MB, 349026 rules) and free RAM drops to 126~132 MB
  Just clicking "update filters" made the free RAM drop to 108 MB

No crash when changing settings, but free RAM drops to around 40 MB for a moment.

I think something is wrong with how much RAM is allocated just to change one setting (like filter update interval)...
Also, it seems that updating the filters lists also requires a lot of RAM, and if somehow it could use the RAM more efficiently, then it could not crash...

[ainar-g]

Thanks for the details. There may be a few issues with how settings are applied, but it would be hard to diagnose without collecting memory profiles by setting debug_pprof: true and saving the contents of http://127.0.0.1:6060/debug/pprof/heap?debug=1.

Some other things that you can try:

1. Using local copies of the filters and their file paths as URLs. This will force AGH to use the file system for scanning rules, so that could reduce the amount of RAM consumed at the cost of extra i/o operations.

2. Set the GOMEMLIMIT environment variable for the AdGuard Home service, which sets a soft RAM limit. This might make the garbage collector work more actively and reduce RAM at the cost of CPU time.

[cjom]

OK, when I have some time I will collect the debug data and also test the GOMEMLIMIT variable, then report here.

EDIT:
Today had little free time but a short test got very promising results...
with GOGC=40 and GOMEMLIMIT=100MiB seems capable of handling 9 lists with total 826000 rules :)
Almost twice the rules tested yesterday!

EDIT:
Nearly 10 seconds after I change "Filter update interval", free RAM drops to little more than 20 MB and CPU usage reaches 89% but at least never crashed.

[cjom]

log1.txt
log2.txt
log3.txt

log1 had GOGC=40 and GOMEMLIMIT=100MiB and changed update interval to see free RAM dropping;
log2 no variables set, "small" filters lists, changed update interval and disabled one filter to see free RAM dropping;
log3 no variables set, "big" filters lists, changed update interval and tried to grab before crash but I don't know if succeed to grab "just before crash".

[ainar-g]

Thanks for testing our the environment variables and attaching the profiles! Unfortunately, the profiles show that most memory is consumed by the filtering engine, so there probably won't be a way to decrease that without a proper rewrite/optimization of the urlfilter module. (@ameshkov, you might be interested in the profiles.)

In the meantime, if the env solution works for you, it's probably the best you can do, along with the filepath-based filters.

[cjom]

I guess, without looking into code, it makes sense that updating filters list temporarily use a lot of memory building a new rules list before replacing the old one, but I don't see why just changing the update interval would require so much memory to be allocated... That's what I tried to log.

On the filepath-based filters, it seems that it still makes copies of local filters lists. I even made it with the exact name and local it is saved, and refreshing makes it overwrite the list with itself. Prabably that could be improved, not making copies of local lists, because it causes unnecessary writing to the router flash...

Thu Mar 23 18:41:17 2023 daemon.err AdGuardHome[4640]: 2023/03/23 18:41:17.783850 [info] saving filter 1679514854 contents to: /opt/AdGuardHome/data/filters/1679514854.txt

[ainar-g]

I've created #5629 to see if we can remove the copying. Thanks for pointing that out.

[jumpsmm7]

@ainar-g please refer back to this study for "extra" research details. #4437

[sshaikh]

1. How or where do we set GOGC=40 and GOMEMLIMIT=100MiB in an OpenWrt environment?
2. Once we copy the filters locally and point AGH to them, how do they get updated? Is that something we have to script up outside of AGH?

[jumpsmm7]

1. How or where do we set GOGC=40 and GOMEMLIMIT=100MiB in an OpenWrt environment?

   2. Once we copy the filters locally and point AGH to them, how do they get updated? Is that something we have to script up outside of AGH?

You would have to run your own external script for updating those local files.

Also, similar to env TZ=/etc/localtime , you would have to pass it as a "pre-arg" env variable on execution of the Adguardhome.go binary.

env GOGC=40 GOMEMLIMIT=100MiB Adguardhome ..... rest of adguardhome running arguments.....

so if you have an init script for starting adguardhome, you would place the env arguments as pre-commands or pre-launch arguments.

[sshaikh]

Thanks for the confirmation on the local files.

Wrt the OpenWrt service, adding procd_set_param env to the adguardhome init.d script seems to be it:

start_service() {
  config_load adguardhome
  config_get WORK_DIR config workdir

  [ -d "$WORK_DIR" ] || mkdir -m 0755 -p "$WORK_DIR"

  procd_open_instance
  procd_set_param env GOMEMLIMIT=100MiB GOGC=40
  procd_set_param command "$PROG" -c /etc/adguardhome.yaml -w "$WORK_DIR" --no-check-update
  procd_set_param stdout 1
  procd_set_param stderr 1
  procd_close_instance
}

[jumpsmm7]

Thanks for the confirmation on the local files.

Wrt the OpenWrt service, adding procd_set_param env to the adguardhome init.d script seems to be it:

start_service() {
  config_load adguardhome
  config_get WORK_DIR config workdir

  [ -d "$WORK_DIR" ] || mkdir -m 0755 -p "$WORK_DIR"

  procd_open_instance
  procd_set_param env GOMEMLIMIT=100MiB GOGC=40
  procd_set_param command "$PROG" -c /etc/adguardhome.yaml -w "$WORK_DIR" --no-check-update
  procd_set_param stdout 1
  procd_set_param stderr 1
  procd_close_instance
}

Yep for openwrt, that works perfectly. For Entware or other router implementations it might have to be adapted per setup. For openwrt, procd takes care of the "logic" as long as you follow openwrts template. For Entware, it would have to be listed as a "pre-arg".

[cjom]

2. Once we copy the filters locally and point AGH to them, how do they get updated? Is that something we have to script up outside of AGH?

I have the following command running once a week in the router:
curl -f -s -q -K /opt/AdGuardHome/agh_filters_list | grep -Ev '^(\!|\#|[[:space:]]*$)' | sed -e '/^0\.0\.0\.0 /s/$/\^/' | sed -e 's/^0\.0\.0\.0 /\|\|/' | sort -u > /tmp/joinedfilters.txt

where /opt/AdGuardHome/agh_filters_list is a text file with the filters url one per line, like this:
url = "https://adguardteam.github.io/HostlistsRegistry/assets/filter_1.txt"

edit: I forgot to mention I stop and restart AdGuard before and after updating the lists, because of the memory crash and also to make the list (re)load.

[sshaikh]

I went much simpler and have a list of wgets followed by a restart of agh, while disabling filter updates in the webui.

Doing this once a day has halved the memory agh uses, with no router crashes so far.

[Sakura-Luna]

I added a GoodbyeAds, on Docker with 1 core 512mb memory, updating rules or custom rules will inevitably lead to freezes or crashes, the log does not contain any errors.

[adoyle-h]

Same issue. When the filters too much, the AdGuardHome processes crashes by OOM.

fatal error: runtime: out of memory

runtime stack:
runtime.throw({0x9dcd96, 0x16})
        runtime/panic.go:1047 +0x4c fp=0x2171eac sp=0x2171e98 pc=0x4eea0
runtime.sysMapOS(0x5000000, 0x400000)
        runtime/mem_linux.go:187 +0x138 fp=0x2171ed8 sp=0x2171eac pc=0x28390
runtime.sysMap(0x5000000, 0x400000, 0x1e0a0e8)
        runtime/mem.go:142 +0x40 fp=0x2171ee8 sp=0x2171ed8 pc=0x27d9c
runtime.(*mheap).grow(0x1af2368, 0x1)
        runtime/mheap.go:1522 +0x2c0 fp=0x2171f38 sp=0x2171ee8 pc=0x3e140
runtime.(*mheap).allocSpan(0x1af2368, 0x1, 0x0, 0x14)
        runtime/mheap.go:1243 +0x1d4 fp=0x2171fc4 sp=0x2171f38 pc=0x3d60c
runtime.(*mheap).alloc.func1()
        runtime/mheap.go:961 +0x84 fp=0x2171fe8 sp=0x2171fc4 pc=0x3d0b0
runtime.systemstack()
        runtime/asm_arm.s:317 +0x60 fp=0x2171fec sp=0x2171fe8 pc=0x8a0ec


goroutine 19 [running]:
runtime.systemstack_switch()
        runtime/asm_arm.s:274 +0x4 fp=0x3c58b90 sp=0x3c58b8c pc=0x8a080
runtime.(*mheap).alloc(0x1af2368, 0x1, 0x14)
        runtime/mheap.go:955 +0x58 fp=0x3c58bb0 sp=0x3c58b90 pc=0x3d00c
runtime.(*mcentral).grow(0x1af2e98)
        runtime/mcentral.go:246 +0x64 fp=0x3c58bd0 sp=0x3c58bb0 pc=0x276c0
runtime.(*mcentral).cacheSpan(0x1af2e98)
        runtime/mcentral.go:166 +0x114 fp=0x3c58c10 sp=0x3c58bd0 pc=0x27234
runtime.(*mcache).refill(0x400be088, 0x14)
        runtime/mcache.go:182 +0x18c fp=0x3c58c40 sp=0x3c58c10 pc=0x26a3c
runtime.(*mcache).nextFree(0x400be088, 0x14)
        runtime/malloc.go:855 +0x84 fp=0x3c58c64 sp=0x3c58c40 pc=0x1c7a0
runtime.mallocgc(0x80, 0x8de190, 0x1)
        runtime/malloc.go:1042 +0x5c0 fp=0x3c58c9c sp=0x3c58c64 pc=0x1cf18
runtime.growslice(0x4ff6700, 0x9, 0x8, 0x1, 0x8de190)
        runtime/slice.go:274 +0x4b8 fp=0x3c58cc4 sp=0x3c58c9c pc=0x6b320
github.com/AdguardTeam/urlfilter/lookup.getRuleShortcuts(0x4ffb130)
        github.com/AdguardTeam/urlfilter@v0.17.0/lookup/shortcutstable.go:129 +0xe4 fp=0x3c58cf4 sp=0x3c58cc4 pc=0x48bc2c
github.com/AdguardTeam/urlfilter/lookup.(*ShortcutsTable).TryAdd(0x421ddd0, 0x4ffb130, 0x64fb2eac000f8592)
        github.com/AdguardTeam/urlfilter@v0.17.0/lookup/shortcutstable.go:55 +0x1c fp=0x3c58d40 sp=0x3c58cf4 pc=0x48b638
github.com/AdguardTeam/urlfilter.(*NetworkEngine).AddRule(...)
        github.com/AdguardTeam/urlfilter@v0.17.0/networkengine.go:84
github.com/AdguardTeam/urlfilter.NewDNSEngine(0x20b4e40)
        github.com/AdguardTeam/urlfilter@v0.17.0/dnsengine.go:108 +0x59c fp=0x3c58db8 sp=0x3c58d40 pc=0x48c458
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).initFiltering(0x2247730, {0x0, 0x0, 0x0}, {0x22fdef0, 0x5, 0x6})
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:847 +0x98 fp=0x3c58de0 sp=0x3c58db8 pc=0x50c698
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).setFilters(0x2247730, {0x22fdef0, 0x5, 0x6}, {0x0, 0x0, 0x0}, 0x0)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:423 +0x100 fp=0x3c58e34 sp=0x3c58de0 pc=0x50a508
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).enableFiltersLocked(0x2247730, 0x0)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filter.go:662 +0x450 fp=0x3c58f78 sp=0x3c58e34 pc=0x509a00
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).EnableFilters(0x2247730, 0x0)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filter.go:629 +0x7c fp=0x3c58f94 sp=0x3c58f78 pc=0x509528
github.com/AdguardTeam/AdGuardHome/internal/home.startDNSServer()
        github.com/AdguardTeam/AdGuardHome/internal/home/dns.go:437 +0xcc fp=0x3c58fcc sp=0x3c58f94 pc=0x8573e8
github.com/AdguardTeam/AdGuardHome/internal/home.run.func1()
        github.com/AdguardTeam/AdGuardHome/internal/home/home.go:603 +0x14 fp=0x3c58fec sp=0x3c58fcc pc=0x8692ac
runtime.goexit()
        runtime/asm_arm.s:831 +0x4 fp=0x3c58fec sp=0x3c58fec pc=0x8bc10
created by github.com/AdguardTeam/AdGuardHome/internal/home.run
        github.com/AdguardTeam/AdGuardHome/internal/home/home.go:602 +0xad0

[Lichtenshtein]

env GOGC=40 GOMEMLIMIT=100MiB Adguardhome ..... rest of adguardhome running arguments.....

How to correctly write this in a systemd service file? Is this correct?

<...>
[Service]
<...>
Environment="GOGC=40"
Environment="GOMEMLIMIT=100MiB"
ExecStart=/home/adguard/adguardhome <...>
<...>

//update

Yep. I lost access to the device after a week. Once a week, adguard updates its lists. How to properly limit the memory for a go application using systemd?

//update2

Any help?

[Impact123]

The unit has a EnvironmentFile definition so you can simply put the variables into /etc/sysconfig/AdGuardHome in a format like this

GOGC=40

and restart the service

# systemctl restart AdGuardHome.service

You can validate if it worked with something like this

# cat /proc/$(pgrep AdGuardHome)/environ | tr '\0' '\n' | grep ^GO
GOGC=40

The /etc/sysconfig folder might not exist. Just mkdir it. A little bit late but might be useful for people in the future.

[Le-chiffree]

To summarize how to:

Edit file by:

nano /etc/init.d/adguardhome

add line after:
procd_open_instance

procd_set_param env GOMEMLIMIT=100MiB GOGC=40

Save and reboot

[marcel13000]

Hello, did you manage to solve the problem? My router ax3600 crashes as soon as I run adguard

[Le-chiffree]

Yes this solution works for me and my friend with AX3600 router. Follow the steps which I made and reboot. After refresh of Adguard it should works. just to make sure have you followed this installation on Openwrt? https://openwrt.org/docs/guide-user/services/dns/adguard-home Without that it will not work properly. I keep fingers crossed Karol

…

On Sat, 16 Mar 2024 at 13:43, marcel13000 ***@***.***> wrote: Hello, did you manage to solve the problem? My router crashes as soon as I run adguard — Reply to this email directly, view it on GitHub <#5606 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXRAE5NUDMUUDKQX5SJM5YTYYQ45VAVCNFSM6AAAAAAV7EZ7SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRHE3TMMBRGM> . You are receiving this because you commented.Message ID: ***@***.***>

[cjom]

Hello, did you manage to solve the problem? My router ax3600 crashes as soon as I run adguard

Keep your ad block list small. Maybe start with two and test.
Even so it might crash when updating lists, but there's some parameter in init script to restart adguard when it crashes.

Edit: Here's the line I have in /etc/init.d/adguardhome:
procd_set_param respawn 3600 60 0 # respawn automatically if something died

[privacy-advo]

@ainar-g
Do you have an update on this issue?

[ainar-g]

There is no update. AdGuard Home needs RAM to keep and update filtering-rule engines. The larger your lists are, the more RAM is necessary.

I'm not sure if there's anything to do in this issue,so I'm going to close it.

[Le-chiffree]

@privacy-advo please check my comment [on Mar 6] and add one line:

Edit file by:

nano /etc/init.d/adguardhome

add line in above file after linke:

procd_open_instance

procd_set_param env GOMEMLIMIT=100MiB GOGC=40

Save and reboot

Then your router will not fall

[findus]

For me setting GOMEMLIMIT=100MiB GOGC=40 wasnt enough with a router with 1GiB ram. The updating seems to be multi threaded, adding GOMAXPROCS=1 somehow helps preventing spikes.