Log-Spam: GetWorldFromContextObject called with a NULL game instance object

Conan Exiles PC Discussion
1

Game mode: Online private
Type of issue: Crash / Performance / Misc
Server type: PvE
Region: US

Server-logs have been getting spammed with the following line:
LogEngine:Warning: GetWorldFromContextObject called with a NULL game instance object.
This line gets spammed several times per second from the moment the server boots up to the moment it shuts down. Our server has also been crashing a few times per day (one to three) and we think this is the cause. However, we have no idea what is causing this ‘GetWorldFromContextObject’-problem.

We have noticed this in our logs since the latest Turan DLC update. It is possible that this warning appeared in our logs before that, but definitely not in the massive quantities it is appearing in now.

We think this might be the cause of our server crashes as we’ve also seen fatal errors regarding not enough memory. Our server is hosted privately by g-portal and they say our server has enough memory so I’m guessing it’s just the absurd amount of warning-messages that’s causing this problem to result in crashes?

Our server runs an extensive mod-list which I can provide in private messages to any professional who can help me out. The same goes for the full server logs.

Due to my little knowledge regarding this specific warning, I don’t know which other info to provide. However, I’m more than willing to provide answers to any questions there might be.

Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:

  1. Start up the server
  2. Logs get spammed with the warning-message provided in the section above.
  3. Server runs usually for several hours appearing quite fine gameplay-wise
  4. Server crashes after running about 10+ hours and then sometimes crashes one or two more times before our scheduled daily restart
  5. After the scheduled daily restart, everything appears normal again for several hours, as mentioned in step 4.

Due to the complexity of the problem I have no clue how to actually reproduce the error besides the steps given above, although obviously this is quite a unique case and I know that the problem can’t be reproduced with the steps provided above.

Anyway, thank you for your time and effort.

Kind regards

2

Hey @SilverJustice

Thanks for reporting this. We’ll send it to our team and see if they can reproduce it on their end so they can look into what could be causing this issue. :slight_smile: