Dear Maintainer,


When running biglybt the aethread2:parked instruction causes a memory leak over time that leads to a system crash due to leaked memory. The only way to fix the issue is to restart the system after crashing java. The system has a variable amount of time before the crash, 2 hours to 16 hours while slowly leaking memory that will lead to a kernel crash. Cleanly shutting down bigly does not release the memory.

unreferenced object 0xffff9e6e0d660aa0 (size 96):
  comm "AEThread2:parke", pid 4510, jiffies 4295360367
  hex dump (first 32 bytes):
    01 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  ....kkkkkkkkkkkk
    42 45 35 33 41 45 43 30 31 42 46 30 44 44 39 38  BE53AEC01BF0DD98
  backtrace (crc 702bc8d4):
    __kmalloc_noprof+0x300/0x430
    __d_alloc+0x169/0x220
    d_alloc+0x19/0x90
    lookup_one_qstr_excl+0x55/0xa0
    do_unlinkat+0x16f/0x330
    __x64_sys_unlink+0x3f/0x70
    do_syscall_64+0x82/0x190
    entry_SYSCALL_64_after_hwframe+0x76/0x7e
unreferenced object 0xffff9e6f227d41e0 (size 96):
  comm "Global Status C", pid 4521, jiffies 4295502874
  hex dump (first 32 bytes):
    01 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  ....kkkkkkkkkkkk
    43 45 46 45 34 34 45 33 44 45 39 46 31 34 36 31  CEFE44E3DE9F1461
  backtrace (crc 30cbb68c):
    __kmalloc_noprof+0x300/0x430
    __d_alloc+0x169/0x220
    d_alloc+0x19/0x90
    lookup_one_qstr_excl+0x55/0xa0
    do_unlinkat+0x16f/0x330
    __x64_sys_unlink+0x3f/0x70
    do_syscall_64+0x82/0x190
    entry_SYSCALL_64_after_hwframe+0x76/0x7e

pid 4521 occurs 13 times aethread2 will crash and get restarted by bigly eating up all of the memory.