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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
-+--
Reporter:  guest |Owner:  igloo  
Type:  bug   |   Status:  closed 
Priority:  high  |Milestone:  6.8
   Component:  Compiler  |  Version:  6.4.2  
Severity:  normal|   Resolution:  fixed  
Keywords:|   Difficulty:  Unknown
  Os:  Windows   | Testcase:  N/A
Architecture:  x86   |  
-+--
Changes (by neil):

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

Comment:

 On my computer I can replicate this bug using GHC 6.4.2, but not using
 6.6.1 or 6.7. I guess that means it got fixed.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
-+--
Reporter:  guest |Owner:  igloo  
Type:  bug   |   Status:  new
Priority:  high  |Milestone:  6.8
   Component:  Compiler  |  Version:  6.4.2  
Severity:  normal|   Resolution: 
Keywords:|   Difficulty:  Unknown
  Os:  Windows   | Testcase:  N/A
Architecture:  x86   |  
-+--
Comment (by igloo):

 Hmm, I can no longer reproduce this, even after having gone back and
 installed GHC 6.6 again, and put it first in my PATH. Can't reproduce it
 in a mingw terminal either.

 It's not impossible that, when I thought I could reproduce it before, I
 was confused by processes that have terminated staying around in process
 explorer for several seconds.

 Can anyone else reproduce this bug?

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
-+--
Reporter:  guest |Owner:  igloo  
Type:  bug   |   Status:  new
Priority:  high  |Milestone:  6.8
   Component:  Compiler  |  Version:  6.4.2  
Severity:  normal|   Resolution: 
Keywords:|   Difficulty:  Unknown
  Os:  Windows   | Testcase:  N/A
Architecture:  x86   |  
-+--
Changes (by simonmar):

  * priority:  normal => high

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
--+-
 Reporter:  guest |  Owner:  igloo  
 Type:  bug   | Status:  new
 Priority:  normal|  Milestone:  6.8
Component:  Compiler  |Version:  6.4.2  
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:  N/A   |   Architecture:  x86
   Os:  Windows   |  
--+-
Changes (by igloo):

  * testcase:  => N/A

Comment:

 This is reproducible for me with wobth GHC 6.4.2 and 6.6 under cygwin,
 running
 `ghc q.hs -o q` and then `./q`.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
---+
  Reporter:  guest |  Owner:  igloo  
  Type:  bug   | Status:  new
  Priority:  normal|  Milestone:  6.8
 Component:  Compiler  |Version:  6.4.2  
  Severity:  normal| Resolution: 
  Keywords:| Os:  Windows
Difficulty:  Unknown   |   Architecture:  x86
---+
Changes (by simonpj):

  * milestone:  => 6.8
  * owner:  => igloo

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[Neil Mitchell]

Hi


I'm not doubting that it's genuine -- but can anyone make a reproducible
test case?

The test case I put in the bug report makes it 100% reproducable on
both my machines. I guess that means its a machine specific bug.

Thanks

Neil



Simon

| -Original Message-
| From: [EMAIL PROTECTED]
[mailto:glasgow-haskell-bugs-
| [EMAIL PROTECTED] On Behalf Of Lennart Augustsson
| Sent: 04 August 2006 13:47
| To: Bulat Ziganshin
| Cc: GHC; glasgow-haskell-bugs@haskell.org
| 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,
| >  Bulatmailto:[EMAIL PROTECTED]
| >
| > ___
| > Glasgow-haskell-bugs mailing list
| > Glasgow-haskell-bugs@haskell.org
| > http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
|
| ___
| Glasgow-haskell-bugs mailing list
| Glasgow-haskell-bugs@haskell.org
| http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs


___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
---+
  Reporter:  guest |  Owner: 
  Type:  bug   | Status:  new
  Priority:  normal|  Milestone: 
 Component:  Compiler  |Version:  6.4.2  
  Severity:  normal| Resolution: 
  Keywords:| Os:  Windows
Difficulty:  Unknown   |   Architecture:  x86
---+
Comment (by simonpj):

 Sigbjorn says "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?"

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [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" <[EMAIL PROTECTED]>

To: "Bulat Ziganshin" <[EMAIL PROTECTED]>
Cc: "GHC" <[EMAIL PROTECTED]>; 
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,
 Bulatmailto:[EMAIL PROTECTED]

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs


___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[Simon Peyton-Jones]

I'm not doubting that it's genuine -- but can anyone make a reproducible
test case?

Simon

| -Original Message-
| From: [EMAIL PROTECTED]
[mailto:glasgow-haskell-bugs-
| [EMAIL PROTECTED] On Behalf Of Lennart Augustsson
| Sent: 04 August 2006 13:47
| To: Bulat Ziganshin
| Cc: GHC; glasgow-haskell-bugs@haskell.org
| 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,
| >  Bulatmailto:[EMAIL PROTECTED]
| >
| > ___
| > Glasgow-haskell-bugs mailing list
| > Glasgow-haskell-bugs@haskell.org
| > http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
| 
| ___
| Glasgow-haskell-bugs mailing list
| Glasgow-haskell-bugs@haskell.org
| http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[Lennart Augustsson]

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,
 Bulatmailto:[EMAIL PROTECTED]

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs


___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[Bulat Ziganshin]

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,
 Bulatmailto:[EMAIL PROTECTED]

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

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

[GHC]

#840: GHC on "loosing" its handles takes 100% CPU
-+--
Reporter:  guest |Owner: 
Type:  bug   |   Status:  new
Priority:  normal|Milestone: 
   Component:  Compiler  |  Version:  6.4.2  
Severity:  normal| Keywords: 
  Os:  Windows   |   Difficulty:  Unknown
Architecture:  x86   |  
-+--
On Windows, GHC 6.4.2, the following program:

 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.

 If "ghci" is used as the argument instead of "ghc", then both ghc and
 ghci are left running, with ghc on 100% CPU time.

 In contrast, if hugs or Yhc or edit (or pretty much any program on my
 system) is run in exactly the same way, they terminate as soon as the
 main program is finished.

 I have replicated this bug on two separate machines, with the following
 similarities/differences.

 Both Windows XP
 One logged in as admin, one logged in as a restricted user
 One AMD 750Mhz, one Pentium 4 HT
 Both GHC 6.4.2

 Simon Peyton-Jones is unable to replicate this using a Windows laptop.

 (Additional reports of success/failure on this issue would be appreciated)

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs