Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

task_policy_set TASK_CATEGORY_POLICY: (os/kern) invalid argument (4) Console Error Message #145

Closed
pjpreilly opened this issue Apr 5, 2023 · 4 comments
Closed

task_policy_set TASK_CATEGORY_POLICY: (os/kern) invalid argument (4) Console Error Message #145

pjpreilly opened this issue Apr 5, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@pjpreilly
Copy link

4/5/23 6:20:52.767 PM [0x0-0x2b02b].org.chromium.Chromium: [1309:48131:0405/182052.766960:ERROR:process_mac.cc(124)] task_policy_set TASK_CATEGORY_POLICY: (os/kern) invalid argument (4)

  • macOS X Lion
  • Build 1124040
  • macbook 4,1

Constant Console output every few seconds
possibly a 32 bit kernel issue....
@pjpreilly pjpreilly added the bug Something isn't working label Apr 5, 2023
@krackers
Copy link

krackers commented Apr 5, 2023 •
edited
Loading

Related change: https://source.chromium.org/chromium/chromium/src/+/31020ea48de075377d69fb64c1268e7c7bf0ddf0

Not clear why exactly it causes an issue though, the actual syscall remains unchanged from before. It's possible that it was always erroring for you, but now that they actively change the priority more frequently, you're seeing more errors?

@pjpreilly
Copy link
Author

It's possible that it was always erroring for you, but now that they actively change the priority more frequently, you're seeing more errors?

The error is non-existent in the current stable..... fwiw

@pjpreilly
Copy link
Author

I stand corrected... similar error on stable but not as often.....

4/5/23 9:10:13.595 PM [0x0-0x15015].org.chromium.Chromium: [195:52995:0405/211013.593912:ERROR:process_mac.cc(64)] task_policy_get TASK_CATEGORY_POLICY: (os/kern) invalid argument (4)

4/5/23 9:10:13.595 PM [0x0-0x15015].org.chromium.Chromium: [195:52995:0405/211013.593976:ERROR:process_mac.cc(95)] task_policy_set TASK_CATEGORY_POLICY: (os/kern) invalid argument (4)

blueboxd pushed a commit that referenced this issue Apr 14, 2023
@edx246
[ios] Add finch params for Foreground Refresh
a3f8f5b 
(cherry picked from commit 2ecfdcd)

Bug: 1418430
Change-Id: I5a7680c22c6fb0af345d39bb23ee691c42fee08e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4300422
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: edchin <edchin@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1111983}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4303133
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: edchin <edchin@google.com>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/branch-heads/5615@{#145}
Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd pushed a commit that referenced this issue May 9, 2023
@robbiemc
iwa: Check for null WebAppProvider in ChromeBrowsingDataModelDelegate
9511881 
This is a speculative fix based on the stack trace in the crash
report. WebAppProvider can be null on ChromeOS in certain cases, which
will be changed/fixed soon, but this will handle the null case in
the meantime.

(cherry picked from commit 4ba71ed)

Bug: 1427992, 1311065
Change-Id: If5dfca0194764f2e1f738a9c424c0b8bee624ff4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4383196
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1123907}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4383715
Owners-Override: Srinivas Sista <srinivassista@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Srinivas Sista <srinivassista@chromium.org>
Cr-Commit-Position: refs/branch-heads/5672@{#145}
Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd pushed a commit that referenced this issue May 27, 2023
@adangla
[iOS] Enable edit button when no active but inactive tabs
9649237 
When a user is in the regular tab grid, the "Close All" option should be
available if there is inactive tab to close even if there is no actives.
This CL add dynamic update to the Edit button in the following scenario:
* When the regular tab grid is empty but there is inactive tabs then
"Edit" button is available and only have "Close All" options
See video:
https://drive.google.com/file/d/1yDpOQjaMNaqyLbCOTlFTT68ctFWZHpMl/view?usp=share_link
* When there is no active nor inactive then "Edit" is not available
See screenshot:
https://drive.google.com/file/d/1U_6s-UQBYjYZgte_6GbN0rukRz29qAGC/view?usp=share_link
* For incognito, the "Edit" button should behave as before
See video:
https://drive.google.com/file/d/1Z7EJnpHT4X9G8KcrtrYursPPcfj0MGDC/view?usp=share_link

(cherry picked from commit 9bee1ec)

Fixed: 1434217
Change-Id: I8e14eff68554f1252647f67f685339fc6e46b467
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4481598
Reviewed-by: Louis Romero <lpromero@google.com>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Aliona Dangla <alionadangla@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1137170}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4498428
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Auto-Submit: Aliona Dangla <alionadangla@chromium.org>
Cr-Commit-Position: refs/branch-heads/5735@{#145}
Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
@krackers
Copy link

krackers commented Jun 4, 2023

I'm assuming that whatever is being passed to task_policy_set probably wasn't supported in 10.7. I don't really want to dig through the kernel source to see when exactly support for this was added, the solution either way is probably to just wrap this in an @available

blueboxd pushed a commit that referenced this issue Sep 10, 2023
@fergald
Move deprecate-unload flag to the deprecated flags section.
480c229 
(cherry picked from commit d08e2c0)

Bug: 1432116,1472288
Change-Id: If363270b971584cc7c4717805d137cfeed04152c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4764528
Auto-Submit: Fergal Daly <fergal@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1182184}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4779739
Commit-Queue: Prudhvikumar Bommana <pbommana@google.com>
Owners-Override: Prudhvikumar Bommana <pbommana@google.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Prudhvikumar Bommana <pbommana@google.com>
Cr-Commit-Position: refs/branch-heads/5938@{#145}
Cr-Branched-From: 2b50cb4-refs/heads/main@{#1181205}
blueboxd pushed a commit that referenced this issue Nov 6, 2023
Roll Chrome Win64 PGO Profile
8c0abff 
Roll Chrome Win64 PGO profile from chrome-win64-6045-1696614294-8df28bb22d8071db0e9e2c5ba184874386b4f705.profdata to chrome-win64-6045-1696636250-669acfb4898056f3e02517d47eded063bbc18e51.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win64-chromium-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome-m119.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I37fd0995c375b7f0c0251ef4ce5ff935a8824eae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4920306
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6045@{#145}
Cr-Branched-From: 905e8bd-refs/heads/main@{#1204232}
blueboxd pushed a commit that referenced this issue May 16, 2024
Roll Chrome Win64 PGO Profile
8bc1f7d 
Roll Chrome Win64 PGO profile from chrome-win64-6367-1711129065-61a9f2317a93c4a9e019132eaa2ee729d11fc46d-73505ebaf922c5ea595491516502214af19090b0.profdata to chrome-win64-6367-1711149022-754eff8f1cbdab41da20f0fa4dcaca31d50d0f0e-8356c80d5c1f9b10c3f9535bd53faecae9152d59.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win64-chromium-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome-m124.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Icc48f9f7c50750f0860a5dbecf58b6d50aa0bcdd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5369184
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6367@{#145}
Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pjpreilly @krackers @blueboxd