167851 2017-02-04 23:53:08 -0800 Leaks bot should use WebKit2 2018-12-06 13:42:14 -0800 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 69543 P2 Normal --- 1 kling webkit-unassigned ap kling lforschler oldest_to_newest 1273362 0 kling 2017-02-04 23:53:08 -0800 I think we should switch over the leaks bot to using WebKit2. It's super red anyway, and any burndown effort would be better spent on WK2 issues than WK1 ones, in my opinion. 1273363 1 kling 2017-02-04 23:56:45 -0800 Actually, I'm really lost in how the bots are set up, so I'm unassigning it from myself. @Alexey: do you agree that we should do this, and if so, do you think it would be easy? 1273375 2 ap 2017-02-05 08:42:38 -0800 I agree that testing wk2 would be much better. Reconfiguring bots is easy, but first, we need to figure out how to do this in principle. A naive approach would result in only seeing UI process leaks. Unrelated to this, we should switch the bot to Sierra ASAP. It has a fix for a huge networking leak that adds a lot of noise. I'll take care of this. 1273376 3 kling 2017-02-05 08:46:35 -0800 Absolutely agreed about Sierra. A slightly less naive approach could simply run "leaks" on each of our processes (WKTR, WebContent, Networking, Databases) and concatenate the results. I think it would still be useful, and we'd want to see leaks in all processes anyway. 1485800 4 ap 2018-12-06 13:42:14 -0800 *** This bug has been marked as a duplicate of bug 69543 ***