RESOLVED FIXED Bug 78189
kill-old-processes should kill gcc and clang 
https://bugs.webkit.org/show_bug.cgi?id=78189
Summary kill-old-processes should kill gcc and clang
Ryosuke Niwa
Reported 2012-02-08 17:45:10 PST
We've just had an issue where a stale clang process was using 7GB of RAM on Chromium Mac Release (Perf) bot. To mitigate issues like this in the future, we should kill gcc and clang instances in kill-old-processes
Attachments
Add gcc and clang to the list of processes to kill (1.26 KB, patch)
2012-02-08 17:51 PST, Ryosuke Niwa 		no flags
DetailsFormatted DiffDiff
Added "clang" (1.28 KB, patch)
2012-02-08 18:48 PST, Ryosuke Niwa 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Ryosuke Niwa
Comment 1 2012-02-08 17:51:31 PST
Created attachment 126209 [details] Add gcc and clang to the list of processes to kill
Lucas Forschler
Comment 2 2012-02-08 18:43:53 PST
i think you might want just 'clang' in there as an option also
Ryosuke Niwa
Comment 3 2012-02-08 18:48:17 PST
Created attachment 126217 [details] Added "clang"
Ryosuke Niwa
Comment 4 2012-02-08 18:57:09 PST
(In reply to comment #2) > i think you might want just 'clang' in there as an option also That's a good idea. Done.
Eric Seidel (no email)
Comment 5 2012-02-09 00:57:41 PST
Comment on attachment 126217 [details] Added "clang" OK.
WebKit Review Bot
Comment 6 2012-02-09 01:18:54 PST
Comment on attachment 126217 [details] Added "clang" Clearing flags on attachment: 126217 Committed r107195: <http://trac.webkit.org/changeset/107195>
WebKit Review Bot
Comment 7 2012-02-09 01:18:59 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.