You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my vrising server logs I see at /opt/stacks/vrising/data, I can see this entry:
Registered WarEventMapNode in Chunk: 15,18
Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
Triggering AutoSave 2171!
I am wondering if I've caused this, on my 2nd try at installing docker-vrising and if you are able to advise what I can do to fix it, thank you.
I set everything up for the first time yesterday and it was running like a dream, total memory usage in debian 12 on my Dell Wyse 5070 was about 50%.... Brilliant thank you for your work making this docker-vrising server.
Today saw the filesystem was running out of space, I was a plank and had installed on the 16GB flash storage. So today have re-installed everything again on the 128GB SSD.
The vrising server seems to be working ok on this 2nd install, but now total system usage is over 70%.
The container is using about same memory usage as yesterday:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
**************** vrising 81.75% 4.041GiB / 7.581GiB 53.31% 19.7MB / 1.74MB 1.27GB / 513MB 91
yesterday could see on top available mem was about 4500, today's install its at around 2k:
Hello,
In my vrising server logs I see at /opt/stacks/vrising/data, I can see this entry:
Registered WarEventMapNode in Chunk: 15,18
Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
Triggering AutoSave 2171!
I am wondering if I've caused this, on my 2nd try at installing docker-vrising and if you are able to advise what I can do to fix it, thank you.
I used your docker-vrising by following this guide: https://pimylifeup.com/v-rising-dedicated-server-linux/
(I am a complete beginner at using unix and docker)
I set everything up for the first time yesterday and it was running like a dream, total memory usage in debian 12 on my Dell Wyse 5070 was about 50%.... Brilliant thank you for your work making this docker-vrising server.
Today saw the filesystem was running out of space, I was a plank and had installed on the 16GB flash storage. So today have re-installed everything again on the 128GB SSD.
The vrising server seems to be working ok on this 2nd install, but now total system usage is over 70%.
The container is using about same memory usage as yesterday:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
**************** vrising 81.75% 4.041GiB / 7.581GiB 53.31% 19.7MB / 1.74MB 1.27GB / 513MB 91
yesterday could see on top available mem was about 4500, today's install its at around 2k:
top - 12:45:05 up 1:07, 1 user, load average: 0.96, 1.09, 1.19
Tasks: 155 total, 2 running, 153 sleeping, 0 stopped, 0 zombie
%Cpu(s): 35.5 us, 14.7 sy, 0.0 ni, 49.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 7762.8 total, 163.4 free, 5715.1 used, 2135.8 buff/cache
MiB Swap: 977.0 total, 512.2 free, 464.8 used. 2047.7 avail Mem
8547 root 20 0 15.6g 3.4g 117172 S 49.0 45.1 43:37.55 VRisingServer.e
18679 root 20 0 109300 93432 4324 S 44.7 1.2 0:01.62 /usr/share/webm
1 root 20 0 168388 11456 7804 R 25.5 0.1 3:36.88 systemd
18699 root 20 0 118388 102196 4008 S 19.5 1.3 0:00.59 /usr/share/webm
8584 root 20 0 2050824 11024 11024 S 2.6 0.1 2:20.74 winedevice.exe
8550 root 20 0 13832 2996 1712 S 1.7 0.0 1:23.93 wineserver64
9724 root 20 0 105496 103096 5344 S 1.7 1.3 0:59.41 stats.pl
47 root 39 19 0 0 0 S 0.3 0.0 0:01.12 khugepaged
543 root 20 0 1183272 26532 9520 S 0.3 0.3 0:21.44 fail2ban-server
692 root 20 0 2428972 57724 31364 S 0.3 0.7 0:03.46 dockerd
18469 root 20 0 11624 5432 3284 R 0.3 0.1 0:00.77 top
copied and attached my vrising server logs... cheers
vrising server log.txt
The text was updated successfully, but these errors were encountered: