We get the attached callstack of a crash when cooking the dedicated server build targeting Linux. Everything seems fine when building the game for Windows.
attaching the call-stack just in case, because I don’t see that it made it with the post.
Hi Daniel, can I check into more context please? Is this a solid repro? Are you able to reproduce it with a default version of the engine (ideally one you can send us so we can dig into the details, or failing that would you be able to gather a crash dump and symbol information we can look at?)
Thanks!
Geoff Stacey
Developer Relations
Thanks Daniel,
If this is a solid repro (which the error seems to imply that it is) then tracking back from a break point, or potentially a full crash dump would be a good shout for isolating this, initially focus on finding which asset this belongs to. From the error, it looks like there is an issue with the asset in that there isn’t curve data - I’d double check that this exact setup builds fine with windows as well, and triple check that asset which is being passed in!
Geoff
I did attach a fuller callstack btw, it’s attached to the case
Hi Daniel,
Apologies, I missed that attached callstack. Agreed, I don’t think this is an asset issue in itself since it does build elsewhere - I am curious if is somehow isn’t getting imported in correctly either due to a file system/URI type issue, or some other quirk going on.
Just to confirm - is this a good repro on Linux?
Geoff
[mention removed] I have isolated the issue to at least one asset .. Whenever I build it I get the asserts. The weird thing is after all the asserts I get a window with “Status: Valid, Attributes: Valid” and the file displays correct in-engine."
The assert also looks like it isn’t failing because of the assert itself but because of a memory safety issue. CurveNumVertices has garbage data sometimes.
Hi Daniel,
It could be worth running this with address sanitizer, since it sounds like this could be pointing to deleted data, and that would pick it up earlier in the process.
Geoff
The engine is slightly modified but not in any ways that touch this. I’ll try to gather as much stuff as I can and get back to you. The project is huge, so isolating this could be tricky. All I know right now is that it only happens in Linux builds.
So, the problem here is that this doesn’t happen on a normal build in Windows, which leads me to believe that while I’m still gonna hunt for the asset, the asset itself might not be the issue? Everything works great on windows, this error only shows up on the Linux server build we’re attempting to do for our dedicated server.