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

Undo stack has potential to run out of memory #2

Open
GoogleCodeExporter opened this issue Mar 31, 2015 · 0 comments
Open

Undo stack has potential to run out of memory #2

GoogleCodeExporter opened this issue Mar 31, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

There is currently no limit on the number of actions that can be undone.
The undo stack stores a complete snapshot of the tile id's of every tile on
the map every time any editing is performed. When editing a large map over
a long period, there exists a high chance for out of memory exceptions so
occur.

Original issue reported on code.google.com by [email protected] on 29 May 2008 at 11:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant