Try disabling counters too, they can produce quite a lot data On Thu, Mar 5, 2015 at 5:08 AM, Grzegorz Sobański <[email protected]> wrote:
> Hi, > > We are looking for a source of memory leak in our app. Unfortunately we > have problems with stability when using mono profiler. > After running the app for about 5 minutes with the profiler enabled, it > stops answering requests, don't crash, but just stops working. (Without > profiling it will run for hours). > > So I have few questions: > 1. Is this some known problem with stability while profiling? > 2. Even when launched as: > mono --gc=sgen --profile=log:heapshot,heapshot=ondemand program.exe > profiler still generates around 50MB/min output (specifying > noalloc,nocalls does not change it). > Is it possible to launch profiler in mode heapshot=ondemand with > everything else disabled? I would in effect like to minimize profiler > impact, preferably to zero in normal run, and only do two heap snapshots > (at start and after an hour). > > Running on mono 3.12, Ubuntu 14.04. > > Best regards > > -- > Grzegorz > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
