Skip to content
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.

got a System.OutOfMemoryException #59

Closed
pinopino opened this issue Aug 28, 2015 · 6 comments
Closed

got a System.OutOfMemoryException #59

pinopino opened this issue Aug 28, 2015 · 6 comments

Comments

@pinopino
Copy link

i'm interest in helios. but i got a System.OutOfMemoryException when i ran TimeService example on single local machine. sorry i can't support the stacktrace info, but below is the method throw this exception (it's in helios-1.4.1\src\Helios\Concurrency\Impl\DedicatedThreadPoolFiber.cs):

public void Add(Action op)
{
     if (Running)
         _threadPool.QueueUserWorkItem(() => Executor.Execute(op));
}

os: window 7 ultimate 64 bit
memory: 16g

@kklldog
Copy link

kklldog commented Dec 22, 2015

me too.....

@samcov
Copy link

samcov commented Feb 28, 2016

I too have seen this! I first saw it in Akka's TimeService sample, and wondered if it was Actor related.

I later tried Helios's version and the same problem occurred.

This is obviously a Helios issue, and it's a real show stopper!

@samcov
Copy link

samcov commented Feb 29, 2016

Just noticed that Helios is depreciated in favor of DotNetty from Azure.

@Aaronontheweb
Copy link
Member

#75 related - looking into it.

@Aaronontheweb
Copy link
Member

99% sure the issue here is the unnecessary allocation of new delegates.... This might be a 1-line fix. Let's see.

@Aaronontheweb
Copy link
Member

Fixed as part of 2.1 using the new APIs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants