-
Notifications
You must be signed in to change notification settings - Fork 5
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
Semantic pointer names may consume all RAM when iterating/recursing #244
Labels
Milestone
Comments
My first instinct is to limit the length of the generated name. It's solely to give the Semantic Pointer a human recognizable name, but that function is lost at a certain length anyways. |
arvoelke
added a commit
that referenced
this issue
May 1, 2020
5 tasks
Great, I've suggested PR #246 to truncate the names. |
arvoelke
added a commit
that referenced
this issue
May 29, 2020
Fixes #244. 1 KB was chosen somewhat arbitrarily, but it seems long enough to capture the majority of use cases where someone might want to read the name, while being a cheap amount of memory relative to the resource requirements of the semantic pointer itself and how it will be used.
arvoelke
added a commit
that referenced
this issue
May 29, 2020
Fixes #244. 1 KB seems long enough to capture the majority of use cases where someone might want to read the name, while being a cheap amount of memory relative to the resource requirements of the semantic pointer itself and how it will be used.
jgosmann
pushed a commit
that referenced
this issue
Jun 14, 2020
Fixes #244. 1 KB seems long enough to capture the majority of use cases where someone might want to read the name, while being a cheap amount of memory relative to the resource requirements of the semantic pointer itself and how it will be used.
jgosmann
pushed a commit
that referenced
this issue
Jun 14, 2020
Fixes #244. 1 KB seems long enough to capture the majority of use cases where someone might want to read the name, while being a cheap amount of memory relative to the resource requirements of the semantic pointer itself and how it will be used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Self-binding to a depth of 20-30 can easily consume all of the available RAM (the example here is 33MB but in my application it was consuming 38GB of RAM). Specifically, iteratively/recursively building up a semantic pointer may cause its
name
to grow exponentially in length. I accidentally 'crashed' my desktop a few times trying to figure out what was going on here. Minimal example:The text was updated successfully, but these errors were encountered: