This is just to keep track of the fact that we've had to disable PGO in some way for the Chromium sandbox code on Windows x64 builds. We should see if we can re-enable this when we update to a newer Chromium commit.
See user story.
Move process sandboxing bugs to their new, separate component. (Sorry for the bugspam; filter on 3c21328c-8cfb-4819-9d88-f6e965067350.)
Component: Security → Security: Process Sandboxing
Created attachment 8797400 [details] [diff] [review] Remove PGO exception for sharedmem_ipc_client.cc This problem with PGO builds appears to have gone now: https://treeherder.mozilla.org/#/jobs?repo=try&revision=8ab49f568aca4f2a6a4b36d9f4558eb7151ad8f0 MozReview-Commit-ID: Qx44MNtns8
Attachment #8797400 - Flags: review?(mh+mozilla)
Assignee: nobody → bobowen.code
Status: NEW → ASSIGNED
Attachment #8797400 - Flags: review?(mh+mozilla) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/cad4dafdc225 Remove PGO exception for sharedmem_ipc_client.cc. r=glandium
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox52: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
You need to log in before you can comment on or make changes to this bug.