You are not logged in.

#1 2020-06-15 19:16:34

barlog
Member
Registered: 2018-09-29
Posts: 4

OOM Killer kills my Intellij IDEA

Hi.

I have a desktop computer with 32Gb RAM.

❯ free -m
              total        used        free      shared  buff/cache   available
Mem:          32122       17122        2016       12002       12983        2552
Swap:             0           0           0

I use Intellij IDEA. It's a java IDE. It's memory usage limited to 4Gb.

But very often, almost always, IDEA killed by OOM-Killer and i don't understand why. With this log is used 2821588kB. Computer have much more.

Out of memory: Killed process 146214 (java) total-vm:16840132kB, anon-rss:2821588kB, file-rss:0kB, shmem-rss:108kB, UID:1000 pgtables:7404kB oom_score_adj:0
5.7.2-zen1-1-zen

Could anybody help me to find a problem please?

Indexing invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
CPU: 7 PID: 164052 Comm: Indexing Tainted: G        W         5.7.2-zen1-1-zen #1
Hardware name: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI/X570 I AORUS PRO WIFI, BIOS F12f 05/28/2020
Call Trace:
 dump_stack+0x66/0x90
 dump_header+0x4a/0x1f7
 oom_kill_process.cold+0xb/0x10
 out_of_memory+0x199/0x770
 __alloc_pages_nodemask+0x1564/0x1680
 ? __alloc_pages_nodemask+0x15a0/0x1680
 pagecache_get_page+0xf0/0x560
 ? __do_page_cache_readahead+0xa5/0x1b0
 filemap_fault+0x692/0xa40
 ? alloc_set_pte+0x112/0x600
 ? filemap_map_pages+0x268/0x3d0
 __do_fault+0x38/0xd0
 handle_mm_fault+0xf3a/0x16c0
 ? __switch_to_asm+0x34/0x70
 do_user_addr_fault+0x209/0x4e0
 page_fault+0x34/0x40
RIP: 0033:0x7efde601e2e1
Code: Bad RIP value.
RSP: 002b:00007efcf4d04bb0 EFLAGS: 00010206
RAX: 00007efd68087800 RBX: 00007efd68087910 RCX: 0000000000000000
RDX: 00007efcf4d05af0 RSI: 0000000775b004d0 RDI: 00007efcf4d04b30
RBP: 00007efcf4d04bc0 R08: 0000000000000100 R09: 00007efd68088d80
R10: 00007efde668249c R11: 0000000775b01298 R12: 00007efd68087910
R13: 00007efcf4d04c50 R14: 0000000000000000 R15: 00007efd68087800
Mem-Info:
active_anon:1825777 inactive_anon:3179486 isolated_anon:0
 active_file:96 inactive_file:57 isolated_file:0
 unevictable:12 dirty:244 writeback:0 unstable:0
 slab_reclaimable:47027 slab_unreclaimable:140723
 mapped:166835 shmem:3180908 pagetables:8600 bounce:0
 free:49258 free_pcp:157 free_cma:0
Node 0 active_anon:7303108kB inactive_anon:12717944kB active_file:748kB inactive_file:228kB unevictable:48kB isolated(anon):0kB isolated(file):0kB mapped:667340kB dirty:976kB writeback:0kB shmem:12723632kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 1832960kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
Node 0 DMA free:15884kB min:32kB low:44kB high:56kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15996kB managed:15884kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
lowmem_reserve[]: 0 3443 32013 32013 32013
Node 0 DMA32 free:121328kB min:7264kB low:10788kB high:14312kB reserved_highatomic:0KB active_anon:1348688kB inactive_anon:1691464kB active_file:4kB inactive_file:0kB unevictable:0kB writepending:0kB present:3615960kB managed:3615952kB mlocked:0kB kernel_stack:212kB pagetables:880kB bounce:0kB free_pcp:248kB local_pcp:0kB free_cma:0kB
lowmem_reserve[]: 0 0 28569 28569 28569
Node 0 Normal free:59820kB min:60284kB low:89536kB high:118788kB reserved_highatomic:2048KB active_anon:5954420kB inactive_anon:11026480kB active_file:1084kB inactive_file:0kB unevictable:48kB writepending:976kB present:29871616kB managed:29261824kB mlocked:48kB kernel_stack:18828kB pagetables:33520kB bounce:0kB free_pcp:380kB local_pcp:0kB free_cma:0kB
lowmem_reserve[]: 0 0 0 0 0
Node 0 DMA: 1*4kB (U) 3*8kB (U) 1*16kB (U) 1*32kB (U) 3*64kB (U) 0*128kB 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15884kB
Node 0 DMA32: 225*4kB (UME) 151*8kB (UE) 111*16kB (UME) 77*32kB (UME) 79*64kB (UME) 43*128kB (UME) 34*256kB (UME) 167*512kB (UM) 10*1024kB (UM) 0*2048kB 0*4096kB = 121356kB
Node 0 Normal: 3993*4kB (UM) 1753*8kB (UE) 1089*16kB (UE) 382*32kB (UE) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 59644kB
Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
3181244 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap  = 0kB
Total swap = 0kB
8375893 pages RAM
0 pages HighMem/MovableOnly
152478 pages reserved
0 pages hwpoisoned

oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-2.scope,task=java,pid=163996,uid=1000
Out of memory: Killed process 163996 (java) total-vm:16775012kB, anon-rss:3280020kB, file-rss:0kB, shmem-rss:328kB, UID:1000 pgtables:8320kB oom_score_adj:0
oom_reaper: reaped process 163996 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:328kB

Last edited by barlog (2020-06-15 20:41:27)

Offline

#2 2020-06-16 09:42:20

barlog
Member
Registered: 2018-09-29
Posts: 4

Re: OOM Killer kills my Intellij IDEA

Ok. The problem was in IOMMU. I disabled it with kernel parameters iommu=off amd_iommu=off and in BIOS settings. And after this problem is gone.

Offline

#3 2020-06-16 12:10:19

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,404

Re: OOM Killer kills my Intellij IDEA

total-vm:16840132kB

That number equals 16 GiB memory.
Maybe you told Intellij to use max 4 GiB per java VM instance instead of total memory ?

The zen kernel you're running makes many low level changes, did you try with stock kernel ?

As for disabling IOMMU :
Your post indicates your motherboard uses a X570 chipset, so you probably have an AMD processor .
Disabling IOMMU can have a severe impact on the performance of AMD systems using 64-bit software and cause hard-to-troubleshoot issues.

I've used AMD systems (Opteron and Threadripper processors, workstation / small server type motherboards ) for over a decade now.
Many of the advantages AMD has over competitors come from their use of IOMMU , NUMA and other design choices.

In my opinion an AMD system with IOMMU disabled is great for 32-bit OSes, but broken for 64-bit OS .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB