Re: [GHC] #2185: Memory leak with parMap

2010-05-26 Thread GHC
#2185: Memory leak with parMap
-+--
  Reporter:  igloo   |  Owner:  simonmar
  Type:  bug | Status:  closed  
  Priority:  high|  Milestone:  6.14.1  
 Component:  Runtime System  |Version:  6.8.2   
Resolution:  fixed   |   Keywords:  
Difficulty:  Moderate (less than a day)  | Os:  Unknown/Multiple
  Testcase:  |   Architecture:  Unknown/Multiple
   Failure:  Runtime performance bug |  
-+--
Changes (by simonmar):

  * status:  new = closed
  * resolution:  = fixed


Comment:

 Fixed:

 {{{
 Tue May 25 08:04:35 PDT 2010  Simon Marlow marlo...@gmail.com
   * Make sparks into weak pointers (#2185)
   The new strategies library (parallel-2.0+, preferably 2.2+) is now
   required for parallel programming, otherwise parallelism will be lost.
 }}}

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:10
GHC http://www.haskell.org/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] #2185: Memory leak with parMap

2010-04-01 Thread GHC
#2185: Memory leak with parMap
-+--
  Reporter:  igloo   |  Owner:  simonmar
  Type:  bug | Status:  reopened
  Priority:  high|  Milestone:  6.14.1  
 Component:  Runtime System  |Version:  6.8.2   
Resolution:  |   Keywords:  
Difficulty:  Moderate (less than a day)  | Os:  Unknown/Multiple
  Testcase:  |   Architecture:  Unknown/Multiple
   Failure:  Runtime performance bug |  
-+--
Changes (by simonmar):

  * priority:  normal = high
  * difficulty:  Unknown = Moderate (less than a day)
  * milestone:  6.12 branch = 6.14.1


Comment:

 The [http://hackage.haskell.org/package/parallel new parallel package] on
 Hackage fixes the space leak in this program (change `rnf` to `rdeepseq`
 to compile it).  I'm leaving the ticket open and moving it onto the 6.14.1
 branch, because we still need to change the GC policy so that sparks are
 not treated as GC roots.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:9
GHC http://www.haskell.org/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] #2185: Memory leak with parMap

2009-04-12 Thread GHC
#2185: Memory leak with parMap
-+--
Reporter:  igloo |Owner:  simonmar
Type:  run-time performance bug  |   Status:  reopened
Priority:  normal|Milestone:  6.12 branch 
   Component:  Runtime System|  Version:  6.8.2   
Severity:  normal|   Resolution:  
Keywords:|   Difficulty:  Unknown 
Testcase:|   Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
-+--
Changes (by igloo):

  * milestone:  6.10 branch = 6.12 branch

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:7
GHC http://www.haskell.org/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] #2185: Memory leak with parMap

2008-07-28 Thread GHC
#2185: Memory leak with parMap
--+-
 Reporter:  igloo |  Owner:  simonmar   
 Type:  run-time performance bug  | Status:  reopened   
 Priority:  normal|  Milestone:  6.10 branch
Component:  Runtime System|Version:  6.8.2  
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Changes (by simonmar):

  * status:  closed = reopened
  * component:  Compiler = Runtime System
  * resolution:  fixed =

Comment:

 unfixed.  Sparks really should be treated as GC roots, because many uses
 of par rely on this behaviour (including most of the strategies library).

 I don't have any ideas for how to fix this yet.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:4
GHC http://www.haskell.org/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] #2185: Memory leak with parMap

2008-06-19 Thread GHC
#2185: Memory leak with parMap
--+-
 Reporter:  igloo |  Owner:  simonmar   
 Type:  run-time performance bug  | Status:  closed 
 Priority:  normal|  Milestone:  6.10 branch
Component:  Compiler  |Version:  6.8.2  
 Severity:  normal| Resolution:  fixed  
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Changes (by simonmar):

  * status:  new = closed
  * resolution:  = fixed

Comment:

 Now fixed, and I've added the program to our test suite.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:3
GHC http://www.haskell.org/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] #2185: Memory leak with parMap

2008-03-31 Thread GHC
#2185: Memory leak with parMap
--+-
 Reporter:  igloo |  Owner:  simonmar   
 Type:  run-time performance bug  | Status:  new
 Priority:  normal|  Milestone:  6.10 branch
Component:  Compiler  |Version:  6.8.2  
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Changes (by simonmar):

  * owner:  = simonmar
  * milestone:  6.8.3 = 6.10 branch

Comment:

 I think sparks are currently treated as roots by the GC, which is wrong.
 I won't get around to fixing this in 6.8.3, but I'll do it in the new GC
 code in 6.10.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:2
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs


[GHC] #2185: Memory leak with parMap

2008-03-29 Thread GHC
#2185: Memory leak with parMap
-+--
Reporter:  igloo |   Owner: 
Type:  run-time performance bug  |  Status:  new
Priority:  normal|   Milestone:  6.8.3  
   Component:  Compiler  | Version:  6.8.2  
Severity:  normal|Keywords: 
  Difficulty:  Unknown   |Testcase: 
Architecture:  Unknown   |  Os:  Unknown
-+--
 With the attached `All.hs`, if you run the program without any arguments
 (so that it uses `parMap rnf` in `gen_blocks_list`) then its memory usage
 keeps going up, even though at the top level it's just running the same
 computation 5 times in a row. Memory usage goes up to over 100M.

 If you give an argument (any argument, so that it uses `map` instead) then
 memory usage is constant and only a few megs.

 Happens in 6.8.2 and the HEAD.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185
GHC http://www.haskell.org/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] #2185: Memory leak with parMap

2008-03-29 Thread GHC
#2185: Memory leak with parMap
--+-
 Reporter:  igloo |  Owner: 
 Type:  run-time performance bug  | Status:  new
 Priority:  normal|  Milestone:  6.8.3  
Component:  Compiler  |Version:  6.8.2  
 Severity:  normal| Resolution: 
 Keywords:| Difficulty:  Unknown
 Testcase:|   Architecture:  Unknown
   Os:  Unknown   |  
--+-
Comment (by igloo):

 Forgot to say: Compiling with
 {{{
 ghc -Wall -fforce-recomp All.hs --make -fasm -O2 -threaded -fglasgow-exts
 -funbox-strict-fields -fbang-patterns -debug
 }}}
 I haven't experimented with other flags.

-- 
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2185#comment:1
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs