Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

15
  • 5
    $\begingroup$ Wow, quite a bit of RAM available there ;-) Does changing $HistoryLength=0 show any effect? $\endgroup$ Commented Nov 10, 2014 at 14:56
  • $\begingroup$ Thanks for your fast reply. No doesn't have any effect. I will add it directly. It seems that the filter just soaks up my memory ;) $\endgroup$ Commented Nov 10, 2014 at 15:02
  • $\begingroup$ quite a bit of RAM available, yes. But at some point even 96 GB are gone ... ;) $\endgroup$ Commented Nov 10, 2014 at 15:05
  • $\begingroup$ Does this continue indeterminately, or is there a cap after which use of memory doesn't raise any more? Nothing really guarantees that garbage collectors return conceptually vacant memory right away, and there are many use cases where this makes sense (especially if the collection is not based on reference counting). It may be a bug, but it may also be an internal implementation detail of the collector, for instance considering garbage collection only every N object allocations. $\endgroup$ Commented Nov 10, 2014 at 15:08
  • 1
    $\begingroup$ I applied it several times using Map and Table and the memory consumption raises in each iteration. If i would run it long enough it would certainly kill my computer (which it did already in the real program I use this line). So it never stops or returns the memory... $\endgroup$ Commented Nov 10, 2014 at 15:13