I see that Soar is consuming more and more memory. Does it do some internal logging (sort of history functionality) which I can disable…or is there a known but unfixed memory leak?
Answer from Scott Wallace (Nov. 19, 2001): There are some known memory issues with Soar. The dominating one has a “fix” in Soar 8.4, but the fix is not completely stable. In general, Soar seems to purposely keep around a fair amount of information, just in case it will be needed later. Most of this information gets flushed away when a state is destroyed, but at the top state, information may just accumulate. Soar agents, that perform lots of reasoning on the top state, are likely to suffer the most from this memory issue. Our fix attempts to get around this problem by significantly reducing the amount of memory overhead for the top-state. In Soar 8.4, you can enable it using: #define NO_TOP_LEVEL_REFS If you encounter problems with it, let me know as many details as possible. I may be able to help. Otherwise, you might be able to reduce memory overhead by using a more dynamic goal space. Memory leak in soar_core_utils.c Question from John A. Shue: While trying to debug a memory leak in
Related Questions
- I see that Soar is consuming more and more memory. Does it do some internal logging (sort of history functionality) which I can disable...or is there a known but unfixed memory leak?
- We e already registered with TechSoup but are having problems logging in to our account so we can see our order history and request Windows 7. Who can help?
- Why does my WBC seem to log data quicker when I’m using the internal memory as opposed to logging to my laptop?
