[GHC] #840: GHC on "loosing" its handles takes 100% CPU

[Sigbjorn Finne]

But as long as it's Haskell code consuming all those CPU cycles,
it can't be all bad? :)

If any of you are running into this while invoking "ghci.exe",
you may want to play with using "ghc.exe --interactive" instead
to see if that improves matters. Not using "ghci.exe" avoids
a layer of sub-process'ery and console event handling nonsense;
a culprit, perhaps?

--sigbjorn

----- Original Message ----- 
From: "Lennart Augustsson" <lennart at augustsson.net>
To: "Bulat Ziganshin" <Bulat.Ziganshin at gmail.com>
Cc: "GHC" <trac at galois.com>; <glasgow-haskell-bugs at haskell.org>
Sent: Friday, August 04, 2006 05:46
Subject: Re: [GHC] #840: GHC on "loosing" its handles takes 100% CPU


> It happens all the time to me that GHC doesn't die properly on windows.
> Every so often I have to kill a few straggling ghc processes.  They  
> all spin consuming 100% CPU when this happens.
> 
> -- Lennart
> 
> On Aug 2, 2006, at 10:09 , Bulat Ziganshin wrote:
> 
>> Hello GHC,
>>
>> Wednesday, August 2, 2006, 4:33:09 PM, you wrote:
>>
>>> #840: GHC on "loosing" its handles takes 100% CPU
>>
>>>  import System.Process
>>>  main = runInteractiveCommand "ghc"
>>
>>>  When run terminates immediately, as expected, but leaves an instance
>>>  of ghc running. The ghc process takes up 100% of the CPU time, and
>>>  seemingly does nothing.
>>
>> well, i have similar problem: there are only 256 megs on my machine
>> and sometimes when ghc compilation uses more than 200 megs and starts
>> trashing memory, i tries to stop it by hitting Ctrl-C. in this
>> situation it's rather typical that i got back my console (and rerun
>> ghc) but old GHC process don't killed and continue to compile program.
>> i can investigate it further but don't know what to do. at least it
>> seems that memory trashing is required to uncover this problem. i also
>> should note that i run "ghc --make" from the .cmd file so there is a
>> whole stack of processes runned. may be i just kill higher-level ghc
>> (or even cmd) and lower-level ghc still continue to do it's job? i'm
>> not sure..
>>
>> -- 
>> Best regards,
>>  Bulat                            mailto:Bulat.Ziganshin at gmail.com
>>
>> _______________________________________________
>> Glasgow-haskell-bugs mailing list
>> Glasgow-haskell-bugs at haskell.org
>> http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
> 
> _______________________________________________
> Glasgow-haskell-bugs mailing list
> Glasgow-haskell-bugs at haskell.org
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs