This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi guys, We've got a multithreaded windows app, been running in production for 18mths+. We've seen a couple of occasions now where LS is getting very unhappy doing some basic operation - intermittent failure, not possible to repro I think. Happens seemingly at random, everything is happy, multiple threads all running ok (for several days) then all of a sudden kaboom - LS errors occur for all threads. Logs show this: which i'm pretty sure traces back to TopologicalSort.StackUncheck(). Which is a really weird place to blow up. I know there have been quite a few inheritance changes over the past few months - does this sort of exception ring any bells with you as to possible cause? Any other ideas on where to look in the first instance? thanks justin |
|
|
I think you're right that it's blowing up in TopologicalSort.StackUncheck, and we did make a change a few months back that could result in multiple threads performing a topological sort at the same time -- but the sort is not thread safe (previously it was called only under a lock so this wasn't an issue). I will investigate and hopefully get you a fix tonight. |
|
|
awesome, thanks. |
|
|
Candidate fix committed and will be in the next nightly. Please be aware that we do not have a torture test as part of our build verification tests, so we can't guarantee that this will fix your problem. So please do let us know if you still see errors. But we're pretty sure we've understood the problem and we believe that the change we've made should fix it! |
|