For now I pushed 3 try builds, with sandbox violation logging enabled for all of them: * Sandbox content level 2 ([try](https://treeherder.mozilla.org/jobs?repo=try&revision=8d575e091c9a7948b2d125068a5b011057991ce3)) * Sandbox content level 1 ([try](https://treeherder.mozilla.org/jobs?repo=try&revision=c98a813faf0e45c4adc693199eafa6922174fb71)) * Sandbox content level 3 ([try](https://treeherder.mozilla.org/jobs?repo=try&revision=528982f3b9b267995aaa37e12538b1b348f5b3a4)) Lets see if we can see a pattern for [those different values](https://searchfox.org/mozilla-central/rev/fdb34ddfe30bd54aba991feb72b1476c77938e46/browser/app/profile/firefox.js#1500-1515). Otherwise I hope that once we have the logs in the System log that we do not clean-up those when restarting the machine and that we should be able to look at them even after the machine was used for other jobs.
Bug 1967525 Comment 35 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For now I pushed 3 try builds, with sandbox violation logging enabled for all of them: * Sandbox content level 2 ([try](https://treeherder.mozilla.org/jobs?repo=try&revision=8d575e091c9a7948b2d125068a5b011057991ce3)) * Sandbox content level 1 ([try](https://treeherder.mozilla.org/jobs?repo=try&revision=c98a813faf0e45c4adc693199eafa6922174fb71)) * Sandbox content level 3 ([try](https://treeherder.mozilla.org/jobs?repo=try&revision=617fea2a2d844454539dfe9ddad4bb10753142ac)) Lets see if we can see a pattern for [those different values](https://searchfox.org/mozilla-central/rev/fdb34ddfe30bd54aba991feb72b1476c77938e46/browser/app/profile/firefox.js#1500-1515). Otherwise I hope that once we have the logs in the System log that we do not clean-up those when restarting the machine and that we should be able to look at them even after the machine was used for other jobs.