Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MakinBlaken

Members
  • Joined

  • Last visited

Everything posted by MakinBlaken

  1. That sounds good. I saw the error in the log but I do see on the container it is staying at a low memory usage. It may be my server that’s from 2016 I think. I wanted to eliminate the error before testing that, but if you had that error I will move on to other testing. Thank you for the help.
  2. Very new to hosting servers. I have a question about a memory leak error that is in the logs. I have V Rising setup and running on Steam and searchable. I have 4 friends playing with me and we keep getting studder that gets worse and worse the longer we play. I restart before every session and its not bad. I checked the logs when I start up and I got this: [Server] Startup Completed - Disabling Scene Loading Systems [Server] Shutting down Asynchronous Streaming Registered WarEventMapNode in Chunk: 16,14 Registered WarEventMapNode in Chunk: 16,15 Registered WarEventMapNode in Chunk: 15,16 Registered WarEventMapNode in Chunk: 18,16 Registered WarEventMapNode in Chunk: 16,17 Registered WarEventMapNode in Chunk: 17,17 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. EOS.Session - Entering ModifySessionAsync! 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. I see the solution, I think, to run app with the -diag-job-temp-memory-leak-validation cmd line argument. I thought click on my docker and run Console with this line was the idea but clearly I'm doing that wrong. How do I run the app with the leak validation line? The more simple the explanation the better please. I clearly don't know where to go or how to use this command. Your help is very much appreciated. This is my first server I have actually running publicly.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.