Hi Miguel, > Ok, alternatively get the stack traces for each thread. > > Do this by enumerating all the threads: > > info threads > > And selecting one by one: > > thread 1 > > Then running the command. > > This is a better version of the "t a a bt" command. >
Here is the output: http://hosting.telecoms.bg/~moskov/gdb-mono_backtrace_15.txt.gz We made some tests and here is an test app that seems to reproduce our problem: http://hosting.telecoms.bg/~moskov/WebTest.tar.gz It has 10 user control which are loaded dynamicly after clicking one of 10 buttons. Every user control contains a data grid with 10000 rows. On my test machine which has 256Mb RAM the problem shows after loading the third user control, and top looks like this: Mem: 255756k total, 248120k used, 7636k free, 3544k buffers Swap: 72252k total, 5616k used, 66636k free, 24212k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3388 www-data 15 0 208m 191m 7792 S 0.0 76.8 0:34.05 mono Regards Georgi Moskov _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
