There's a detected issue #1533 regarding race-condition and deadlock. During the discussion, it was suggested that the true fix for this should be carried out in CoreBuildLaunchBarTracker #CoreBuildLaunchBarTracker().

Moreover, CoreBuildLaunchBarTracker looks much more appropriate to start fixing the deadlock, because the deadlock itself initiated by its setActiveBuildConfig implementation: it schedules a Job with resource modifications outside of Workspace control, that initiate another runnable under Workspace control. IMO this unnecessary nesting is the thing that should be fixed.

This issue is raised to keep track of it