http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Rennie, As a matter of fact, no, that was another issue. See the next few posts.http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment9http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment9Sun, 23 Dec 2012 09:05:37 GMTCan this have anything to do with it? http://nikosbaxevanis.com/2010/10/20/adventures-using-rhino-servicebus/http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment8http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment8Sun, 23 Dec 2012 08:42:24 GMTHave you tried using a memory profiler like ANTS Memory Profiler or .NET Memory Profiler(http://memprofiler.com/)?http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment7http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment7Fri, 21 Dec 2012 18:38:32 GMTI had a very similar issue using Lucene in the past. The problem was I upgraded the project to .net 4.0 and Lucene .net was built against an older version. Upgrading to Lucene.Net 2.9.4g and all projects to .NET 4.0 fixed my issue. I feel your pain. To track down my issue I just started deleting functionality until the issue stopped. WinDBG wasn't that helpful in my case.http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment6http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment6Fri, 21 Dec 2012 16:49:58 GMTyeah, sorry for my bad english, what i mean is if gc works or not to know if it's a memory leak problem http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment5http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment5Fri, 21 Dec 2012 16:06:27 GMTmm, That doesn't matter, if we call GC.Collect() when it is 4 GB in size, it should clear 4 GB of waste on its own. If it doesn't, it means that there is something else that is wrong.http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment4http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment4Fri, 21 Dec 2012 15:30:17 GMTso if you call Gc.Collect() every N documents during the test the memory still continue to increase? http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment3http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment3Fri, 21 Dec 2012 15:28:12 GMTmm, We have a way to call GC directly, yes, and no, it doesn't help.http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment2http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment2Fri, 21 Dec 2012 15:19:47 GMTdo you try to explicit call gc when a block of (20k/40k) documents has been imported?http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment1http://ayende.com/160386/ravendb-2-0-stopship-bug-memory-is-nice-let-us-eat-it-all#comment1Fri, 21 Dec 2012 15:19:00 GMT