Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In Manos.IO.Managed/Context.cs, bad synchronization? #133

Open
blucz opened this issue Aug 23, 2011 · 0 comments
Open

In Manos.IO.Managed/Context.cs, bad synchronization? #133

blucz opened this issue Aug 23, 2011 · 0 comments

Comments

@blucz
Copy link

blucz commented Aug 23, 2011

This is happening on windows with ms.net 4.0 with 78f3d16

the 'outstanding' queue is protected by lock(syncRoot) in some places and lock(this) in other places.

Occasionally, I get a crash like this:

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at Manos.IO.Managed.Context.RunOnceNonblocking() in c:\sooloos\sooloos\Cola\Manos\src\Manos.IO\Manos.IO.Managed\Context.cs:line 124
   at Manos.IO.Managed.Context.RunOnce() in c:\sooloos\sooloos\Cola\Manos\src\Manos.IO\Manos.IO.Managed\Context.cs:line 107
   at Manos.IO.Managed.Context.Start() in c:\sooloos\sooloos\Cola\Manos\src\Manos.IO\Manos.IO.Managed\Context.cs:line 100

Changing all of the locks to reference syncRoot seems to fix the problem.

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

No branches or pull requests

1 participant