Bug 39182 - Threadpool bug
Summary: Threadpool bug
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 6.0.99
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Marek Habersack
URL:
Depends on:
Blocks:
 
Reported: 2016-02-27 22:11 UTC by Andy
Modified: 2017-08-23 20:53 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Andy 2016-02-27 22:11:07 UTC
Hi,

This error has come up since I upgraded to Cycle 7 Alpha but it may have been present before:

System.Threading.SynchronizationLockExceptionObject synchronization method was called from an unsynchronized block of code.

at System.Threading.ThreadPoolWorkQueue.SparseArray<T>.Add(T e)
at System.Threading.ThreadPoolWorkQueueThreadLocals.ThreadPoolWorkQueueThreadLocals(ThreadPoolWorkQueue tpq)
at System.Threading.ThreadPoolWorkQueue.EnsureCurrentThreadHasQueue()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Comment 1 Marek Habersack 2016-03-02 13:59:35 UTC
@Andy, would there be a chance for a project which reproduces the issue?
Comment 2 Cody Beyer (MSFT) 2017-08-23 20:53:37 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!