Skip to content
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

[Server] Changing levels to nt_shrine_ctg causes segfault #621

Open
1 of 2 tasks
brysondev opened this issue Sep 19, 2024 · 6 comments
Open
1 of 2 tasks

[Server] Changing levels to nt_shrine_ctg causes segfault #621

brysondev opened this issue Sep 19, 2024 · 6 comments
Labels
Bug Report Bug Reports made through the "Report Issue" interface in GitHub. Map Issues Any issue that only exists on a specific map. Not awarded a bounty.

Comments

@brysondev
Copy link
Contributor

Build Info

20240919_9e83cc3

Description

Changing levels on a dedicated linux server to nt_shrine_ctg causes a segfault. I've attached a crash dump for analysis. It likely happens with maps with displacements, but I cannot confirm that.

To Reproduce

  1. Start server on map that doesn't crash upon launch.
  2. Change map to nt_shrine_ctg (or anything presumably with displacements [unverified])
  3. Server segfaults immediately.

Expected behavior

Server should be able to host nt_shrine_ctg without crashing.

Actual behavior

Server segfaults and reboots.

Operating System

  • Windows
  • Linux

Version/Distro

Debian GNU/Linux bookworm 12.7, Kernel Linux 6.1.0-25-amd64

Machine's CPU

11th Gen Intel(R) Core(TM) i9-11900K

Machine's GPU

No response

GPU's driver

No response

Build's compiler

GNU 11.4.0

Additional context and Screenshots

0c51477b-fd37-4f08-8c99b8a7-94fbf829.dmp.txt
0c51477b-fd37-4f08-8c99b8a7-94fbf829.dmp

@brysondev brysondev added the Bug Report Bug Reports made through the "Report Issue" interface in GitHub. label Sep 19, 2024
@brysondev
Copy link
Contributor Author

We might want to collect a list of maps that cause segfaulting, #592 is related.

@brysondev brysondev added the Map Issues Any issue that only exists on a specific map. Not awarded a bounty. label Sep 19, 2024
@AdamTadeusz
Copy link
Contributor

#28 is probably even more related

@xedmain
Copy link
Contributor

xedmain commented Sep 19, 2024

bullet

@xedmain
Copy link
Contributor

xedmain commented Sep 19, 2024

note that there was research into the topic in the discord, additionally there are "fixed" versions for bullet and shrine available (but their displacements are wacky, but seems to have fixed the crash)

@xedmain
Copy link
Contributor

xedmain commented Sep 19, 2024

sth sth displacements power of 2

@Rainyan
Copy link
Collaborator

Rainyan commented Sep 20, 2024

Would it be worthwhile to convert all of the "Map X crashes" issues into this meta issue: NeotokyoRebuild/neoAssets#1 ? Because trying to forward-port the old maps to be fully compatible might not be a worthwhile venture, if we can simply solve it by recompiling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Bug Reports made through the "Report Issue" interface in GitHub. Map Issues Any issue that only exists on a specific map. Not awarded a bounty.
Projects
Status: No status
Development

No branches or pull requests

4 participants