[Responded] Client crashes whilst using teleport to zone scroll

1. Title: Client crashes whilst using teleport to zone scroll.
2. Reproduction Rate: 2/4
3. Blocker: Yes.
4. Details: Teleporting from Brittany Wharfs to Etceter (Pilgrim Docks) crashed the client happened whilst loading Etceter as scrolls were used up.
5. Steps to Reproduce: Use a teleport to zone scroll to go to Etceter from Brittany Wharfs.
6. User Specs:
   
   
   OS: Windows 10 (10.0.0) 64bit
   CPU: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4) System RAM: 16284
   GPU: NVIDIA GeForce GTX 1060 6GB GPU RAM: 6052
   SotA.Win.64.921.Date.02.28.19
   Area: Novia_R3_City_Brittany_Wharfs
   Area Display Name: Brittany Wharfs
   Loc: (285.8, 38.6, 616.6)
   Debug: Tm92aWFfUjNfQ2l0eV9Ccml0dGFueV9XaGFyZnN8fCgyODUuODAyLCAzOC41NTYsIDYxNi41NjQpfCgwLCAwLjg3NSwgMCwgMC40ODQpfDEzOS4xMjU3fDI3LjMxMzIzfDMuNDA2NjM=​

 

Teleport to friend has problems too:

a) It teleports you to the map instead of into the zone your friend is in
b) The game immediately crashes when you enter the zone.

 

Again, zoning from Brittany Wharfs to Novia Market.

Edit: And again, zoning from Novia Market to Brittany Wharfs, decided to skip the teleport and start on the overworld and then crashed loading into Brittany Wharfs East docks from there.

 

Again, this time I made note that it crashed at 7% Building Map.

 

A crash early in the load process ( <50%) is a strong indicator that there is either file corruption or a video card driver problem. If you are using stream, you can use the steam utility to verify the contents of the install. The other thing would be to check for updated video drivers.

 

I think there's a deeper problem than this with the game. It crashes for both my wife and I a few times a day. We use entirely different computers and installations (Her install is in fact extremely recent because I had rebuild her system from the OS up). It's easiest to trigger if you are alt-tabbed out of the game while changing scenes, but that's not necessary (my wife doesn't do that for example). It just causes it to occur about twice as often. Also, in the case I'm discussing, it's always > 50% when it crashes.

 

Agree. crashes that occur after the 50% mark are less likely to be about install or driver issues. For example, the infamous hang at 93% is a deadlock inside the unity engine that can occur on anyone's machine. Unity receives a crash dump whenever an actual crash to desktop happens. Unity has acknowledged some crash bugs, and is working to address them.
Another thing to try would be to turn off various graphics features in options. You might find a particular graphics option that causes instability for your machine.

More detailed reports about crashes can sometimes illuminate possible work-arounds that we can address at the application level. e.g. this graphics option causes more instability, or when I wear this item, or go to this particular location in a scene. We can often modify the related content to lessen the chance of a Unity crash.

EDIT: Some details I brushed over: "Unity" is the game engine that Shroud uses. Also the 50% I referenced is the progress indicator on the load screen. 50% and below is the time where the scene is loaded (e.g. terrain, trees, rocks, static geometry, some buildings). After 50% is the dynamic content, like mobs, players, decos.

 

I had a crash to desktop happen to me last night teleporting to a zone. First time I have crashed to desktop in ages.

 

I have also crashed a few times trying to teleport either to a friend or teleport to zone and the scrolls were used, started when I was playing on Friday. First time I have crashed to desktop playing this game.

 

May this is a hint: (found in sota_log.txt)

Code:

NetworkingPeer: Connecting to "38.140.214.157:5055"
Network storage reset
AsyncLoadSequence begin. SceneToLoad: Novia_R7_City_Aerie:PlayerSpawnLocation_SW
16:47:23: Loading Scene...
10
16:47:24: Level load loop started.
Size overflow in allocator.

(Filename:  Line: 95)

Could not allocate memory: System out of memory!
Trying to allocate: 18446744072608160268B with 16 alignment. MemoryLabel: Serialization
Allocation happened at: Line:551 in
Memory overview

[ ALLOC_DEFAULT ] used: 4295491446B | peak: 0B | reserved: 5100471286B
[ ALLOC_TEMP_JOB ] used: 1274312B | peak: 0B | reserved: 22020096B
[ ALLOC_TEMP_BACKGROUND_JOB ] used: 0B | peak: 0B | reserved: 1048576B
[ ALLOC_GFX ] used: 887325992B | peak: 0B | reserved: 975895680B
[ ALLOC_CACHEOBJECTS ] used: 759694896B | peak: 0B | reserved: 824088368B
[ ALLOC_TYPETREE ] used: 13912664B | peak: 0B | reserved: 16777216B
[ ALLOC_PROFILER ] used: 336B | peak: 0B | reserved: 4194304B
[ ALLOC_TEMP_THREAD ] used: 156772B | peak: 0B | reserved: 2457600B
Could not allocate memory: System out of memory!
Trying to allocate: 18446744072608160268B with 16 alignment. MemoryLabel: Serialization
Allocation happened at: Line:551 in
Memory overview

[ ALLOC_DEFAULT ] used: 4295491446B | peak: 0B | reserved: 5100471286B
[ ALLOC_TEMP_JOB ] used: 1274312B | peak: 0B | reserved: 22020096B
[ ALLOC_TEMP_BACKGROUND_JOB ] used: 0B | peak: 0B | reserved: 1048576B
[ ALLOC_GFX ] used: 887325992B | peak: 0B | reserved: 975895680B
[ ALLOC_CACHEOBJECTS ] used: 759694896B | peak: 0B | reserved: 824088368B
[ ALLOC_TYPETREE ] used: 13912664B | peak: 0B | reserved: 16777216B
[ ALLOC_PROFILER ] used: 336B | peak: 0B | reserved: 4194304B
[ ALLOC_TEMP_THREAD ] used: 156772B | peak: 0B | reserved: 2457600B


(Filename:  Line: 1114)

Receiving unhandled NULL exception
#0  0x007f8f3d74fc40 in funlockfile
#1  0x007f8f0c08d910 in operator new[](unsigned long, std::nothrow_t const&)
#2  0x007f8f0c08d980 in operator new[](unsigned long, std::nothrow_t const&)
#3  0x007f8f0c08d9c0 in operator new[](unsigned long, std::nothrow_t const&)
#4  0x007f8f0c08db30 in operator new[](unsigned long, std::nothrow_t const&)
#5  0x007f8f0c08dbb0 in operator new[](unsigned long, std::nothrow_t const&)
#6  0x007f8f0c08dc70 in operator new[](unsigned long, std::nothrow_t const&)
#7  0x007f8f0c08de30 in operator new[](unsigned long, std::nothrow_t const&)
#8  0x007f8f0c08de70 in operator new[](unsigned long, std::nothrow_t const&)
#9  0x007f8f0c08ded0 in operator new[](unsigned long, std::nothrow_t const&)
#10 0x007f8f0c08dee0 in operator new[](unsigned long, std::nothrow_t const&)
#11 0x007f8f0c08df00 in start_thread
#12 0x007f8f0c08dfc0 in clone

Another time is was 21GByte that Shrouds wants to allocate (have 8 + 12 swap = 20). The same label: Serialization
After a starting the client again, all was ok. Means it is not reproduce-able for me.

Code:

Desktop is 1920 x 1080 @ 60 Hz
Initialize engine version: 2018.2.20f1 (cef3e6c0c622)
GfxDevice: creating device client; threaded=1
Renderer: AMD CYPRESS (DRM 2.50.0 / 4.15.0-46-generic, LLVM 7.0.0)
Vendor:   X.Org
Version:  4.3 (Core Profile) Mesa 18.2.8
[…]
Default vsync count 1
requesting resize 1920 x 1080
Using native desktop resolution 1920 x 1080
requesting fullscreen 1920 x 1080 at 0 Hz
Desktop is 1920 x 1080 @ 60 Hz
Failed setting thread niceness (priority) to 0 due to EACCES (errno 13) violation. Lowering niceness (raising priority) requires CAP_SYS_NICE or superuser.
[…]
SystemInfo, graphicsDeviceName=AMD CYPRESS (DRM 2.50.0 / 4.15.0-46-generic, LLVM 7.0.0), graphicsMemorySize=1003, graphicsDeviceType=OpenGLCore, operatingSystem=Linux 4.15 Ubuntu 18.04 64bit, processorCount=2, processorType=Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz, systemMemorySize=7976
SotA.Linux.64.922.Date.03.01.19, LocalTime=03.03.2019 13:39:16, Patch=lonely-exterminator
LanguageManager, Language=German, Culture=de-DE, SystemCulture=de-DE, Partner=None

Graphic setting is: simple
Use Camara effects, depth of field, cull intrior objects, "simulate/prieview armor"are on.

 

Interesting, I'll have to remember to check that log next time I crash. I have 32GB of RAM so hopefully it's not an OOM issue.

 

Not to say allocating 16 PetaBytes (18446744072608160268B) is a little intense. Usually this indicates a corrupted file, but in this case i would not be able to load into this scene after re-start.

 

Mine is crashing to the desktop with no log files being created.

 

Tried a Teleport to Zone Scroll from Brittany Wharfs to Etcter Docks. No crash (at least for me). Maybe my system info might help?

Wonder if this might be Video Settings related? (Which sadly are not in the /bug report).

User Specs:
OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz (8) System RAM: 16303
GPU: NVIDIA GeForce GTX 1080 GPU RAM: 8079
SotA.Win.64.924.Date.03.04.19
Area: Novia_R2_City_Etceter/Etceter
Area Display Name: Etceter
Loc: (116.1, 21.1, -55.0)
Debug: Tm92aWFfUjJfQ2l0eV9FdGNldGVyfEV0Y2V0ZXJ8KDExNi4wOTIsIDIxLjA2MSwgLTU1LjA0Nyl8KDAsIDAuODA2LCAwLCAwLjU5Myl8MTA3LjMyODR8MTB8MTIuNzgyMjM=

 

Teleport to Zone - East Vauban Foothills to KnightsWatch (has been happening with recalls, and tele to friends as well - since R63

03/05/2019 14:01
Title:
Reproduction Rate:
Blocker?
Details:
Steps to Reproduce:
User Specs:
OS: Mac OS X 10.14.3
CPU: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12) System RAM: 16384
GPU: AMD Radeon Pro Vega 20 GPU RAM: 4080
SotA.OSX.64.924.Date.03.04.19
Area: Novia_R5_Hills01_01
Area Display Name: East Vauban Foothills
Loc: (124.7, 140.4, -101.4)
Debug: Tm92aWFfUjVfSGlsbHMwMV8wMXx8KDEyNC43MDMsIDE0MC40NCwgLTEwMS40MjIpfCgwLCAwLjk0NiwgMCwgLTAuMzIzKXwyMTcuNzAzN3wxMHw0LjMzOTM0Mw==


Below is beginning of log that MAC reports:
https://drive.google.com/open?id=1gp1eRlRF5xdW8SKBQgnEKgDDXgZwgM88

 

Been getting a lot of these crashes too on teleporting - 3 separate accounts, 3 separate PCs, all Windows machines with Intel 7th and 8th gen CPUs / 1060 or 1070 GFX cards - all drivers etc up to date.

 

Atos noted in discord that crashes in R63 have gone up significantly. So they know it's a real problem.

 

Again, though weirdly whilst harvesting in Novia Market.

Spoiler: Spec

OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4) System RAM: 16284
GPU: NVIDIA GeForce GTX 1060 6GB GPU RAM: 6052
SotA.Win.64.926.Date.03.06.19
Area: POT_forest_metropolis_01_template/Novia Market
Area Display Name: Novia Market
Loc: (48.2, 50.3, 245.2)
Debug: UE9UX2ZvcmVzdF9tZXRyb3BvbGlzXzAxX3RlbXBsYXRlfE5vdmlhIE1hcmtldHwoNDguMjQ4LCA1MC4zNCwgMjQ1LjIxMSl8KDAsIC0wLjAyNywgMCwgLTEpfC0xNjQuNDQ1NXw0Ni4yMDAzNnw5Ljg1MDEzMQ==

 

Build 928 hopes to address the crashes. Time to update!

 

Seems to have done the trick - been teleporting all night no crashes