Suggestion: Turn on +RTS -xt by default
I found it quite surprising and difficult to debug that my heap profile showed no leak while the GC stats showed a clear leak. As a user who is somewhat familiar with this stuff, I was quite surprised that those two data sources didn't agree. I wasn't sure how to determine why they disagreed, since none of the output referenced anything interesting.
I'm not familiar with the reasoning behind disabling -xt by default, but I think it may be easier for users to figure out that they need to *disable* it (since they'll be able to see its results in the heap profile) than to figure out that they need to *enable* it.
Trac metadata
| Trac field | Value |
|---|---|
| Version | 8.2.2 |
| Type | FeatureRequest |
| TypeOfFailure | OtherFailure |
| Priority | low |
| Resolution | Unresolved |
| Component | Runtime System |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture |
Activity
added RTS Tfeature request Trac import labels
I'll admit I don't even see why you would want to disable
-xt. Perhaps Jaffacake can shed some light on this?If there is a good reason why running without
-xtis useful then we'll need to add a way to disable it in order to act on this ticket.Otherwise I would say in the long-run we probably ought to deprecate the option.
Trac metadata
Trac field Value CC - → Jaffacake added Plow label