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

KeyValues uses different memory pool in client & server #1769

Open
SamVanheer opened this issue Jan 9, 2017 · 0 comments
Open

KeyValues uses different memory pool in client & server #1769

SamVanheer opened this issue Jan 9, 2017 · 0 comments

Comments

@SamVanheer
Copy link

The KeyValues class is backed by a memory pool that is used to allocate the objects, their names and their values, if they are small enough. The client uses a pool from the vgui2 library, while the server uses one from vstdlib (though not used in server code anywhere it seems). Making both use the same pool would make things easier.

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

1 participant