-
Notifications
You must be signed in to change notification settings - Fork 1
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
Cleanup more the entities once they get destructed #39
base: master
Are you sure you want to change the base?
Conversation
I tried to use the arrays EmptyEntity::componentOffsets and EmptyEntity::messageHandlers instead, but they are apprently private. This PR is an alternative solution.
|
Can you explain the bug in detail so we can learn? |
Is your hypothesis that one of the components of the entity being destroyed tries to access one of the entity's other components from its destructor? If that's the case, the fix won't help as |
Well that's not it - the only two components with user-defined destructors are TurretComponent and SpawnerComponent. (The latter does have something of a bug of the type I described though - Unvanquished#2233) |
Marking as draft before I find time to test more (probably not soon) |
It looks like this submodule reference had been mistakenly committed. I noticed it because a |
It looks to have been committed in Unvanquished/Unvanquished@4fb94c2 |
Supposedly fixes Unvanquished/Unvanquished#1939