I can't remember if it was threadscope that crashed or the RTS, since I was also having segfaults in the RTS because of this bug, that is fixed in 7.2.2: http://hackage.haskell.org/trac/ghc/ticket/5552

I successfully used threadscope by running my code for fewer iterations to produce a smaller log, and it was helpful to make sure I was dividing work equally between the threads.

I think I still have the log file that was about 1.8GB so I will try running threadscope on it and see what happens.

The performance problems I was having turned out to be fixed completely by changing the GC options passed to the RTS.

On Mon, Oct 10, 2011 at 15:55, Tom Thorne <thomas.thorne21@gmail.com> wrote:

Yes I will try to run threadscope on it, I tried it before and the event log output produced about 1.8GB, and then crashed.

Hi Tom,

I'm one of the TS/ghc-events hackers and I'd like to learn more,

fix it or at least put it on the TS/ghc-events issue tracker

(http://trac.haskell.org/ThreadScope). Could you help me reproduce

the problem? Did ThreadScope crash or RTS? Which versions?

Was it 1.8GB of the log file or RAM? Did you succeed eventually?

Any other TS feedback?

Thank you,

Mikolaj