[GHC] #9539: TQueue can lead to thread starvation

[GHC]

#9539: TQueue can lead to thread starvation
-------------------------------------+-------------------------------------
        Reporter:  jwlato            |                Owner:  (none)
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Core Libraries    |              Version:  7.8.2
      Resolution:                    |             Keywords:  stm
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------
Changes (by dfeuer):

 * status:  closed => new
 * resolution:  fixed =>


Comment:

 I'm 90% confident this is not actually fixed. We now get good results from
 `atomically $ do {...; readTQueue q}`. Unfortunately, I believe the exact
 same problem will still occur as soon as we go a little further, with
 `atomically $ do {... ; !x <- readTQueue q; return x}`. I believe the only
 true solution is to base `TQueue` on a real-time queue rather than an
 amortized one.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9539#comment:12>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler