Open
Bug 1254552
Opened 8 years ago
Updated 10 months ago
DMD auto-triggered threshold reports
Categories
(Core :: DMD, task, P3)
Core
DMD
Tracking
()
NEW
People
(Reporter: froydnj, Unassigned)
Details
Attachments
(1 file)
3.21 KB,
patch
|
Details | Diff | Splinter Review |
It is sometimes useful to trigger reports when memory reaches a certain threshold, rather than trying to ensure that you catch a high memory condition through about:memory.
Reporter | ||
Comment 1•8 years ago
|
||
This patch needs some cleanup (checking for TMP or TMPDIR environment variable, so it works on Windows; we don't have XPCOM niceties, such as they are, available in DMD), but this is the basic idea. Ideally one could set the threshold via a DMD option as well. I'm probably not going to work on this in the immediate future.
Comment 2•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:mccr8, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: froydnj+bz → nobody
Flags: needinfo?(continuation)
Comment 3•2 years ago
|
||
This is kind of a "useful idea with a prototype patch, but not exactly cleaned up enough for landing" so I think that's fine.
Flags: needinfo?(continuation)
Updated•2 years ago
|
Severity: normal → N/A
Priority: -- → P3
Updated•10 months ago
|
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•