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

Inspecting a large enough object will run the gem out of memory #112

Open
martinmcclure opened this issue Mar 19, 2022 · 0 comments
Open
Assignees
Labels
bug Something isn't working important Issue that is fairly high priority

Comments

@martinmcclure
Copy link
Member

It's possible to run the gem out of memory inspecting a sufficiently large object.
We need to decide on a strategy for how to handle inspecting very large objects. Some of the decisions that must be made are

  • How do we decide that an object is big enough to cause problems if inspected normally?
  • What do we present to the user when we can't present the usual inspector?

We should make sure that even in the case of very large objects it is possible to get to all of the information in the object.

@martinmcclure martinmcclure added bug Something isn't working important Issue that is fairly high priority labels Mar 19, 2022
@martinmcclure martinmcclure self-assigned this Mar 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working important Issue that is fairly high priority
Projects
None yet
Development

No branches or pull requests

1 participant