Weird exception on collection

Question

0.00/5 (No votes)

See more:

Hi
I get the below exception when I try to add/insert/remove to a collection (or any operation that changes the collection).
The collection is initialized and the item inserted is not null and of the same type as the collection T.

Can any one give me a clue as to why this happens?

Thanks

The runtime has encountered a fatal error. The address of the error was at 0x60f41744, on thread 0x231c. The error code is 0x80131623. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.

Update:
The collection is an ObservableCollection and I managed to get down to know that it happens on the notify part of the collection changed.
This happens on the UI thread inside a task with the TaskScheduler.FromCurrentSynchronizationContext() option.

The weird thing is if I remove this (TaskScheduler.FromCurrentSynchronizationContext()) option the add/insert/remove action, all seems to work good.

Posted 6-Jan-13 0:34am

Shahare

Updated 6-Jan-13 2:17am

v2

Add a Solution

Comments

OriginalGriff 6-Jan-13 6:50am

Without the relevant code fragments? Probably not.
Use the "Improve question" widget to edit your question and provide better information.

Shahare 6-Jan-13 8:17am

I improved my current findings but I`m not happy with the not understanding part.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Espen Harlinn · Answer 1 · 2013-01-06T00:52:00

Are you manipulating the collection from an asynch event handler running on another thread?

Error 0x80131623 is COR_E_FAILFAST - which is a very generic error generated by Environment.FailFast() which is called when your application is causing an internal invariant to be violated.

Best regards
Espen Harlinn