8000 Shutdown Assert: m_currMap · Issue #79 · conan513/SingleCore_TC · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Shutdown Assert: m_currMap #79

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

Open
Subtixx opened this issue Sep 26, 2017 · 4 comments
Open

Shutdown Assert: m_currMap #79

Subtixx opened this issue Sep 26, 2017 · 4 comments

Comments

@Subtixx
Copy link
Subtixx commented Sep 26, 2017

Description:
The worldserver crashes with an assert of m_currMap

Current behaviour:

SingleCore_TC/src/server/game/Entities/Object/Object.cpp:1865 in GetBaseMap ASSERTION FAILED:
  m_currMap
Segmentation fault

Expected behaviour:
Shutdown without an error

Steps to reproduce the problem:

  1. Start server
  2. let bots join
  3. Try to stop the server (Either with CTRL+C or using server shutdown)
  4. Crash

Branch(es): npcbots

TC hash/commit: 364631d

TDB version: TDB 335.61

Operating system: debian 9

@conan513
Copy link
Owner

what brach is it?

@Subtixx
Copy link
Author
Subtixx commented Sep 27, 2017

npcbots
So default when checking out

Btw I had a lot of trouble getting SingleCore_TC to work. Since it threw a lot of errors with 335.63 So I had to revert back to 335.61.

Never "debugged" with linux, so it's a shame that there is no stacktrace? Else I could investigate further.

EDIT:
Also somehow we have only Level 1 bots, and 2 of them are active and only join the server?

@conan513
Copy link
Owner

as I know there is some issue on debian systems and I don't know why
I have a virtualbox repack, based on arch linux and it's working flawless

@Subtixx
Copy link
Author
Subtixx commented Sep 27, 2017

Is there anyway to get a stacktrace?

conan513 pushed a commit that referenced this issue Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0