Hi,
On 7/2/07, Cedric Vivier [EMAIL PROTECTED] wrote:
On 7/2/07, Rodrigo Kumpera [EMAIL PROTECTED] wrote:
Heap walking is not supported AFAIK. You could, in theory, implement this
feature by extending the garbage collector, but this would require some big
mono hacking, which I think you
Hi,
On 4/19/07, Miguel de Icaza [EMAIL PROTECTED] wrote:
The draft is:
http://www.go-mono.com/archive/1.2.4/
In there, you have this chunk:
In addition to the old Mono.Data.Sqlite, we are now also shipping
Mono.Data.Sqlite2, which is Robert Simpson's Sqlite binding for
.NET
Hi Alan,
On 3/29/07, Alan McGovern [EMAIL PROTECTED] wrote:
I ran it again, and came up with this (startling ;) ) figures for
allocations:
1) type=System.Runtime.Remoti...ing.MonoMethodMessage 4185
1024.1M 256603.6 0.5
System.Threading.ThreadPool:QueueUserWorkItem
Hi,
On 3/30/07, Miguel de Icaza [EMAIL PROTECTED] wrote:
One question: how do I enable the four different profiling modes for
HeapBuddy?
The summary mode is the default. For the others, you just provide the
relevant word on the command line. history, types, backtraces.
You can also turn off
Hey,
On 3/30/07, Alan McGovern [EMAIL PROTECTED] wrote:
Yup, i had noticed that ;) There is something fishy, but i can't find out
what it is. I've run heap-shot and attached and emailed the results in
already. Hopefully they'll make sense to someone. By the looks of it,
there's some kind of
Hi again,
On 3/30/07, Joe Shaw [EMAIL PROTECTED] wrote:
That huge object array, in turn, is referenced by
System.Collections.Queue - System.Net.Socket.Socket, specifically the
readQ member. So basically it means that the readQ member in
System.Net.Socket.Socket is a huge Queue, which
Hi,
On 3/30/07, Alan McGovern [EMAIL PROTECTED] wrote:
That leaves me with the question of how the hell a SocketAsyncResult is 10
megs in size!
It's not the SocketAsyncResult itself that's 10 megs in size, it's the
object array that holds them that is 10 megs in size.
I'm going to do a bit
Hi Alan,
On 3/29/07, Alan McGovern [EMAIL PROTECTED] wrote:
So, the thing is i can't track down what's causing the memory usage in
monotorrent. I have no idea how to even start. I've tried using the built in
profilers, but they require a graceful exit before they output their data,
and
Hi,
On Mon, 2006-08-21 at 22:44 +0200, Lukas Lipka wrote:
attached is a patch to make UnixClient more TcpClient like on 2.0.
Mainly needed to make the Client property public.
Would it violate any current API/ABI restrictions to change Client from
protected to public and add Available and
Hi,
On Fri, 2006-03-31 at 19:19 +0200, Zoltan Varga wrote:
Please-Please file bug reports for the issues that can be considered bugs,
like
the more robust reporting of the stack traces of all threads with SIGQUIT.
issue, which I never heard about before. I can't promise that we will fix all
Hi,
This stretched out a bit more than I originally intended. :)
On Tue, 2006-03-28 at 20:47 -0500, Miguel de Icaza wrote:
What would be the top feature you would like to see in Mono?
Although not really in Mono itself, one thing I would like to see is
better integration with automake.
Hi Paolo,
On Thu, 2005-09-15 at 19:28 +0200, Paolo Molaro wrote:
You need to _run_ it with optimizations enabled:
mono -O=all,-ssapre Benchmark.exe
Building with optimizations enabled has basically no effect.
Is there a reason why all optimizations aren't on by default? I didn't
see
Hi,
On Wed, 2005-07-27 at 10:42 +0200, Mario Sopena wrote:
I'm not Ben but there is a tarball here:
http://www.go-mono.com/packagers/gecko-sharp/gecko-sharp-0.6.tar.gz
Yeah, this is where we've been pointing people who build Beagle as well.
The only problem I found there is that
13 matches
Mail list logo
