New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New World (1063730) #5772
Comments
I couldn't reproduce the crash (loading with existing character worked just fine for me 2 of 2 times). Could you please try the following:
|
Hi @gofman 👋 Going forward I won't use GE to troubleshoot just to limit the problem space. Assume Proton Experimental is being used unless specified.
As far as I know, the official New World client shipped all the correct SDK files for EAC with a fresh install via Steam on Linux. Are you saying that the game didn't package the linux eac dll?
I backed up the eac directory, and placed your attached dll in the eac directory. Launch options: Thanks for your time! EDIT: I haven't used bleeding edge before so I glossed over that in your request. Here's a log using Proton Experimental with bleeding edge specified: |
Hi @gofman GPU: GTX 1060 I removed GE-proton prefix, switched to proton experimental bleeding edge and copied EasyAntiCheat/EasyAntiCheat_x86.dll as you suggested, with PROTON_LOG=1 %command% as launch options. Starting the game and loading a character worked 5 times in a row and i was able to play a little while, then crashed the 6th times i started the game before even being able to load a character |
Thanks for the logs! @masonnl Somehow both your log gives no clue even on immediate crash reason (that's apparently not your fault). Can you please attach dmesg (or 'sudo dmesg' if your system restricts dmesg to root only) output dumped right after the game has crashed? @blae-s Your log does have immediate reason but it suggests some very weird memory corruption reason of which I am unlikely to guess without reproducing. Are there any hints or more details how any of those crashes can be reproduced? I've got a character which I exited the initial ship wreckage / zombies area, got and completed some first "dueling quest" killing some drowners, and loading in to this character. Is that enough? I wasn't able to reproduce any crashes so far. |
Looks to be crashing due to an out of memory dump. Possibly a mem leak or something as it is not an issue with my hardware limitations. dmesg.dump.log As mentioned, this crash occurs very consistently for me. I am not in the tutorial zone of the game, though which it sounds like you may be? I believe I am logged out in a city. |
Hm, if I am not missing something obvious in arithmetic the game takes roughly 10GB of RAM when killed, which is not obviously an issue on 16GB machine. Looks like something potentially explored with the host maybe. Just in case, is it long to get out of tutorial zone to the city and, provided that is not too long and easy to say, how do I quickly get to a city out of tutorial zone? |
Probably takes 10 minutes from opening the game. Just run where it points you, fight the dude with the laser-beam sword, spawn on the beach, and follow the main road into the nearest town (hit 'M' to reveal the map; you will spawn in 1 of 3(?) random areas so the town name will vary). |
Following up on this with some new discoveries: I got to thinking about the oom-killer and it made me realized a couple things:
To help see if I was indeed hitting some system-defined process memory cap I ran the following command in the background while booting: I added a swapfile to my system, made an fstab entry, and rebooted to make sure I was repeating the above experiment with a clean slate. Upon loading in, I again saw the available process memory approach 0, but this time the kernal utilized the swapfile for the (seriously egregious) memory usage and I successfully loaded in. |
I can confirm that the expanded memory availability resolves the crash I was reporting as part of this compatibility report 🎉 To sum up my findings:
|
New World (1063730) Issue transferred from #5774. Compatibility Report
System InformationDistro: Ubuntu 20.04.4 LTS I confirm:
log for experimental (not bleeding edge run): log for 7.0.1: SymptomsTried experimental, 7.0.1, and experimental bleeding edge. It crashes about 2-5 minutes into playing. Early on I was able to play for quite a while, but not that I have about 4-6 hours into the game it crashes every time almost instantly. I am sitting in the wilderness at this point just collecting some ore and hemp and it crashes usually about 3-4 resources nodes into collecting every time. I only see this other New World issue reported: #5772 ReproductionStart steam |
Hello @hagenmt, maybe DXVK is having a vram issue with this hint:
|
Update: I upgraded to Ubuntu 22.04 as soon as it came out few days ago. Didn't help. When proton 7.0.2 came out though shortly after that, also didn't help but I switched to experimental bleeding edge after the 7.0.2 release and it appears the crashes are fixed! Still having the freezes that others have mentioned maybe texture loading related (which have lead to several untimely deaths). But the hard crashes appear to be resolved. |
I'm experiencing crashes/freezes with the game as well, do I add my information in this issue or do I create a new issue? |
Hello @Hydranet, we're using one issue report per unofficially supported game title. This is the right place for all information related to running New World with Proton. |
Compatibility Report
System Information
I confirm:
SymptomsEvery short while my game freezes and crashes, although I'm getting the impression it's happens more when I'm gaming and switch to my other monitor every now and then to do something on my other monitor but I'm not 100% sure. Reproduction
I will do some more testing tomorrow to see what happens if I play for a few hours without switching to my other monitor. If that gives different results I will add it as an update in this post. |
Hello @Hydranet, these look like some lines of interest from your log:
Followed by an access violation (c0000005). I suspect that X (Xwayland) dying hints that there's a video driver issue to ponder. |
Hello @kisak-valve |
Was crashing randomly too much to play, but then I disabled the in-game voice chat and after that no more crashes. |
Thanks - disabling this worked for me too. Up until I tried that I kept getting crashes with: |
Note that the EAC support for this game seems to be semi-broken. You have to wait for it to error out and then immediately log in again without restarting the game every time you start the game. |
Compatibility Report
System Information
I confirm:
SymptomsI have tried all Proton version, including Proton-GE. Game runs fine in all version except for the fact that the game crashes at random time-intervals. I have noticed that whenever I join an OPR/Instance and the game crashes, I will log back on to the OPR/instance and the game wont crash for the entire duration of the OPR/instance (Doesn't matter how long the opr/instance takes) until it is over and I get ported back out. ReproductionStart steam |
From the log: |
Thanks, im pretty new to linux. So I wouldn't know what that means. How do I fix it or further debug it? I restarted the pc without opening anything else other than steam. Not sure if this is helpful at all but I got another log with the same issue. I also ran dmesg and got the SteamLinuxRuntime_soldier log. Let me know if there's anything else I can/should do Thanks :) |
Upgrading my Kernel from 5.10 LTS to 5.15 LTS resolved the issues with game crashing |
Are you still able to reproduce issues with Mesa and up-to-date drivers? If so, can you explain how to reproduce? Thanks! |
Thanks - 7.0-6 works! Is there a regression in newer Proton Versions? |
here's the gist: |
New World Issue transferred from #6920. Compatibility Report
System Information
I confirm:
Proton log as Gist SymptomsThe game stopped launching after the last update on July 6. In steam it has the status "Running", but after a few seconds the game crashes with an error as in the picture. Before the update the game was running without any problems. NOTE: The game starts normal with Proton 7.0-6. ReproductionJust start the game with Proton Experimental or Proton 8.0 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
New world crashing very often during loading screens Issue transferred from #7234. Compatibility Report
System Information
I confirm:
Game always crashes with a bunch of: SymptomsThe game is crashing during loading screen (mostly in bigger cities or crowded places) ReproductionCould be reproduced very well, happening everytime I play the game. I searched the web for err:sync:RtlpWaitForCriticalSection, I found this should have been fixed by release Wine6.1 I tried a lot chaning graphic details, but this seems to be replated to a internet/game server connection timeout issue, or may I misunderstand this? Thanks and best regards kitsab |
[Edit, did not solve the issue - it happened again] Hello, possibly I found something after long repeating duckduckgo - searches. I had the issue trying to logon ~10 times again, after modifying this value it worked instandly - hopefully this solves the problem. Best regards Kitsab |
New World Crashing on Startup Issue transferred from #7341. Compatibility Report
System Information
I confirm:
SymptomsThe game crashes immediately during startup. Reproduction
Have tried multiple versions of Proton, GE-Proton, launch options, etc. |
Hello @bigwheel50, looking at your system information, it looks like Vulkan is broken in general on your system (https://gist.github.com/bigwheel50/9387dd7d7460814ca43f6b0fa78a766f#file-gistfile1-txt-L3573-L3584) I suspect this is from something setting Blind guess, if you completely close Steam, then run |
Thank you for the quick reply! Launching steam through the terminal does seem to impact the |
I've gotten that same error when trying older versions of Proton/GE-Proton as well. As @stiangrindvoll mentioned, the issue started this morning after a large patch. Up until this, things were running smoothly. |
Here is my proton steam log file |
I assume you both have high core count CPUs. Edit: Playing with 16 seems stable so far |
Yes this worked! Thank you @Blisto91 im currently testing with 18. |
Wooo! Can confirm that worked for me as well! 26 still failed, however, I tried the aforementioned 18 count and that did the trick! |
Cool thanks. 26 seemed to do the trick for me, but might be a bit random. Shouldn't hurt the game either way. Edit: actually 26 could still crash ingame at times. 16 seems stable so far |
i had crashes at 18 too, randomly while in the game. At 12, i've had no single crash yet. |
New World eventually hard crashes my machine and have to hard reboot. Compatibility Report
System Information
I confirm:
Symptoms:Game loads in fine, occasionally crashes after character select or sporadically during gameplay. It may be of note that my journal gets flooded with the following log line, on average it's posting the overrun log with different values about every 2-3ms
Example of frequency:
Do not seem to have this log appear in any game besides New World. Game crash in journal after freezing machine Reproduction:
|
I have a similar issue to what @mailhotz is reporting. On my end it doesn't crash the entire OS but the game itself will crash after 2 hours of continuous play. Checking journalctl reveals it spews that message several times per second. System specs: https://gist.github.com/Unaccounted4/2e1ee0dd64ccc5c6801740e3cbe4ab89 Sample of 2 seconds in journalctl:
|
Repeatedly crashing in game after 15-40 minutes of gameplay. Happens in a variety of locations. Startup settings: Here is the ourput of NWerr.log:
The error log shows up to "Fossilize INFO" while starting and then the crash is always "stack smashing detected". I've tried this on Proton 7, 8, 9 beta, and experimental through Steam's compatibility tool. Does anyone have any idea on next steps? I keep crashing in combat and dying. |
The game seems to have a problem with multi-threading and proton, I have been able to achieve stable performance (albeit not great performance) with the following change to my launch options: EDIT: @blae-s why thumbs down? |
Compatibility Report
1063730
System Information
I confirm:
EasyAntiCheat/easyanticheat_x64.so
and connects successfully as shown in the EAC logs generated under~/.cache/com.epicgames.easyanticheat/271/loader.log
. I have been able to play upwards of 10+ hours in the last few days (with crashes as described below).Symptoms
Except in the rare occasion when the game actually loads, it will simply crash to desktop while loading into a character (see STR below).Steps to Reproduce
Scenario 1:
Scenario 2:
The text was updated successfully, but these errors were encountered: