I'm not sure what the rule on mixed line breaks are, but Mono.Data/Provider.cs
has ^M all over it.
%s/^M$//g
(^M being CTRL+V, CTRL+M) fixes this.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
Hello Miguel,
If your team finally decide to go for Madrid option (even Seville
could be nice :-P), some mates and I'd help looking for a place to
host the summit (one of the campus available at this city would be
nice). Even more, I involve myself in finding an University. :-)
Here, at Spain,
El mié, 18-07-2007 a las 10:00 +0200, Marcos Cobeña Morián escribió:
Hello Miguel,
If your team finally decide to go for Madrid option (even Seville
could be nice :-P), some mates and I'd help looking for a place to
host the summit (one of the campus available at this city would be
nice).
My lab works on a peer-to-peer network overlay and we've noticed
recently significant memory issues. Some background...
This application is constantly creating new objects and shortly
thereafter deleting (removing reference to) them
Using a sample run with 150 threads running...
Mono on Linux
Could you post up the detailed stats from heapshot? After the 12 hour run,
how much memory are you using? Are we talking in the gigabyte range, or
megabyte range?
Alan.
On 7/18/07, David Wolinsky [EMAIL PROTECTED] wrote:
My lab works on a peer-to-peer network overlay and we've noticed
Initially 45 MB, 12 hours later 147 MB
Another developer has the heap-shot logs, I'll post those as soon as
possible.
David
Alan McGovern wrote:
Could you post up the detailed stats from heapshot? After the 12 hour
run, how much memory are you using? Are we talking in the gigabyte
range,
I vote for Boston in October.
I really wanted to come to the last one but it coincided with selling
my house and moving so was unable to make it. This year I am really
determined to make it. I've already got a trip scheduled in February
so October sounds great to me.
Cheers,
Joe
On 7/17/07,
Well, after 12 hours at a consistent 25kB/sec, you'd expect to have over 1
gig of memory allocated. As you don't, i think what you're seeing is just
'normal usage' for the non-compacting GC that mono uses. I have a similar
app which uses sockets extensively (50-150 simultaneous connections) and
We run this software on system where memory is a concern. The data that
we presented is our test case system that has 50 nodes all running in
the same mono process. We run only a single node at each site which
initially starts at ~15 MB, we've seen it swell to well over 300 MBs in
a period
I am receiving an error when trying to serialize a class. I am unsure if it
is a bug or if it is something else. The object serializes with out any
problems when I use windows; however, mono complains about an object
reference not being set. Is there any method that anyone can think of that
will
Can we get pkg-config files for mono-data-* packages
please?
See the bug for MonoDevelop and the comment from
Lluis.
http://bugzilla.ximian.com/show_bug.cgi?id=81234
--- Additional Comments From Lluis Sanchez
2007-05-30 10:07 ---
Since there is no .pc file for the mono-data-*
libraries,
We've isolated the problem down to AutoResetEvent...
using System;
using System.Threading;
namespace Ipop {
public class IPOP_Common {
public static void Main() {
AutoResetEvent re = null;
while(true) {
re = new AutoResetEvent(false);
re.Close();
}
}
FYI, this case is only triggered when using gmcs and not mcs.
David
David Wolinsky wrote:
We've isolated the problem down to AutoResetEvent...
using System;
using System.Threading;
namespace Ipop {
public class IPOP_Common {
public static void Main() {
AutoResetEvent re = null;
Drop a bug report to: bugzilla.ximian.com containing that testcase and put
it under the 'compilers' section. It sounds like a gmcs issue.
Alan.
On 7/18/07, David Wolinsky [EMAIL PROTECTED] wrote:
FYI, this case is only triggered when using gmcs and not mcs.
David
David Wolinsky wrote:
Néstor Salceda escribió:
El mié, 18-07-2007 a las 10:00 +0200, Marcos Cobeña Morián escribió:
Hello Miguel,
If your team finally decide to go for Madrid option (even Seville
could be nice :-P), some mates and I'd help looking for a place to
host the summit (one of the campus available at
Alan McGovern wrote:
Drop a bug report to: bugzilla.ximian.com containing that testcase and put
it under the 'compilers' section. It sounds like a gmcs issue.
That's rather a NET_2_0 issue. AutoResetEvent has a different
implementation under 2.0.
Robert
Alan.
On 7/18/07, David Wolinsky
On 7/18/07, Robert Jordan [EMAIL PROTECTED] wrote:
Alan McGovern wrote:
Drop a bug report to: bugzilla.ximian.com containing that testcase and put
it under the 'compilers' section. It sounds like a gmcs issue.
That's rather a NET_2_0 issue. AutoResetEvent has a different
implementation
Hi
Am getting this error while I am trying to connect to the MySql DB. (however
there are no compile time problems) . I am running mono on VM Ware (openSuse
10.2 ).
System.DllNotFoundException: libodbc.so
at (wrapper managed-to-native) System.Data.Odbc.libodbc:SQLAllocHandle
On 7/18/07, Cedric Vivier [EMAIL PROTECTED] wrote:
Looks like the _wapi_private_handles array expands indefinitely but
never shrinks.
Hmm, by shrinks I meant the allocated slots are not reused like they
should because of the Close() I guess.
___
namespace Ipop {
public class IPOP_Common {
public static void Main() {
AutoResetEvent re = null;
while(true) {
re = new AutoResetEvent(false);
re.Close();
}
}
}
}
blows up memory
That depends on the finalizer to run to release memory
Can we get pkg-config files for mono-data-* packages
please?
Sure, which ones do you need?
See the bug for MonoDevelop and the comment from
Lluis.
http://bugzilla.ximian.com/show_bug.cgi?id=81234
--- Additional Comments From Lluis Sanchez
2007-05-30 10:07 ---
Since there is
That case leaks as well.
Regards,
David
Miguel de Icaza wrote:
namespace Ipop {
public class IPOP_Common {
public static void Main() {
AutoResetEvent re = null;
while(true) {
re = new AutoResetEvent(false);
re.Close();
}
}
}
}
blows up
Am 18.07.2007 um 19:54 schrieb David Wolinsky:
That case leaks as well.
Regards,
David
Miguel de Icaza wrote:
re = new AutoResetEvent(false);
re.Close();
That depends on the finalizer to run to release memory from the
unmanaged side, since AutoResetEvent implements
Is Mono supported on Redhat Kernel 2.6?
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/
In fact, I was able to fix the problem.
For some reason in WaitHandle.cs, the line...
safe_wait_handle = new SafeWaitHandle (value, false);
should be...
safe_wait_handle = new SafeWaitHandle (value, true);
(at least it makes sense according to other docs I read)...
second... in
On 7/18/07, I wrote :
Looks like the _wapi_private_handles array expands indefinitely but
never shrinks.
Hmm, by shrinks I meant the allocated slots are not reused like they
should because of the Close() I guess.
I've continued my investigation from the low-level handles.c to the managed.
I'm using a basic RijndaelManaged encrypt/decrypt scenario. It round
trips on .net clr, but depending on my input string length, the mono
implementation crops the end of my string on decrypt. It seems to be
based on the block size, or something. Disclaimer: I'm not an expert
here! As anyone seen
Bugzilla report and patch
Regards,
David
http://bugzilla.ximian.com/show_bug.cgi?id=82134
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
My lab works on a peer-to-peer network overlay and we've noticed
recently significant memory issues. Some background...
This application is constantly creating new objects and shortly
thereafter deleting (removing reference to) them
Using a sample run with 150 threads running...
Mono on Linux
Hello folks,
Thanks for tracking this problem down.
Thanks for pointing out the comment in the source code; I went and
re-read the documentation and I clearly did not understand it the first
time over, because the leak was documented to happen only in the .NET
1.0 and 1.1 scenarios, not
second... in SafeWaitHandle.cs, the line ...
NativeEventCalls.CloseEvent_internal (DangerousGetHandle());
should be...
NativeEventCalls.CloseEvent_internal (handle);
I missed this one, I have now applied this as well.
Miguel
31 matches
Mail list logo
