[CRASH] Kernel Panics on 10.9.5 #113
Labels
bug
Something isn't working
Comments
|
This is a duplicate of #44. The panics do seem to occur for some users more often than others—and some users who rarely experience panics for a while will suddenly start getting them more frequently—but you're definitely not the only one with this issue. The problem is fundamentally a bug in the OS X kernel which Apple fixed in Sierra, and it could in theory be triggered by other software as well—but for whatever reason, Chromium is the only software known to trigger it. The good news is that Krackers and I created a kernel extension which will fix these panics. The simplest way to install it is by using #25. |
|
That's what I get for not exploring better – I always assumed your tool was strictly for updating. Apologies for the unnecessary report, but thank you for pointing me in the right direction (and for the patches)! |
blueboxd
pushed a commit
that referenced
this issue
Nov 30, 2022
on the NTP, no group config is sent for pSuggest as it does not require a header. For that reason, no group ID is being provided for pSuggest. However, to allow local history zps and pSuggest to properly combine on the NTP, server side changes are being made to send group IDs for pSuggest even on the NTP. Currently Chrome drops the group ID from the suggestion if no corresponding group config is present in the response. By retaining those group IDs, this change allows pSuggest and local history ZPS to seamlessly combine on the NTP under the same group, albeit without a header. If pSuggest is not present in the zero-suggest response on the NTP, local history ZPS continues to use the default section for historical zps which comes before the remote zps sections. The existing behavior and the changes in the CL were tested using a demo provided in cl/481213074 (cherry picked from commit e1b4694) Bug: 1343512, 1340079 Change-Id: I7e5f10331431b790fbd67cf24a89bd3878081391 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3957875 Reviewed-by: Tomasz Wiszkowski <ender@google.com> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1060244} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3966909 Cr-Commit-Position: refs/branch-heads/5359@{#113} Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
blueboxd
pushed a commit
that referenced
this issue
Feb 8, 2023
Change-Id: I3ab37134cf91edff6e87987be7cc570736427cdc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4135138 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5481@{#113} Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
blueboxd
pushed a commit
that referenced
this issue
Mar 7, 2023
The rendered zoom factor estimation accounts for the OS font scale and desktop site zoom scale. Currently, if the zoom factor after taking these two factors into account exceeds the maximum display value equivalent of the zoom factor, the value is clamped at the maximum display value. This causes an issue when the display value is calculated from the rendered zoom level for values that overflow, as a result of which a certain range of values up to the maximum displayed value will render the same zoom factor that is equivalent to the clamped (maximum) value. This CL removes removes zoom factor clamping to resolve this issue. This will allow any previously overflowing zoom factor to be rendered without any restrictions and display the expected value on the zoom UI. Sample screenshots for zoom on a desktop site and max OS font: With clamping: https://screenshot.googleplex.com/8fmHzcV4SkUdyp5.png Without clamping: https://screenshot.googleplex.com/C2quBg5AvLsraER.png (cherry picked from commit e606569) Bug: 1395364, 1410135 Change-Id: Id1e2089b911a17d4069f59e8634b22909e2bc638 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4208912 Reviewed-by: Mark Schillaci <mschillaci@google.com> Commit-Queue: Aishwarya Rajesh <aishwaryarj@google.com> Reviewed-by: Jinsuk Kim <jinsukkim@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1099878} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4219316 Cr-Commit-Position: refs/branch-heads/5563@{#113} Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
blueboxd
pushed a commit
that referenced
this issue
Apr 14, 2023
Let fullscreen-within-tab tabs open popups without exiting. The window is not fullscreen and this matches dialog behavior. Add FullscreenMode and FullscreenState types and plumbing. These reflect more granular information for content hosts. Add test coverage for related behaviors; minor refactoring. (cherry picked from commit d3609c1) Fixed: 1413459 Change-Id: Iaf274887b3cf840f7d9aa6c39c26b76623a90e45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255184 Reviewed-by: Avi Drissman <avi@chromium.org> Commit-Queue: Mike Wasserman <msw@chromium.org> Reviewed-by: Brad Triebwasser <btriebw@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1111119} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4301071 Auto-Submit: Mike Wasserman <msw@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/branch-heads/5615@{#113} Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd
pushed a commit
that referenced
this issue
May 9, 2023
This CL will update lacros version in //chrome/LACROS_QA_QUALIFIED_VERSION. This file will be used in Upreving the RootFS-Lacros in the CROS image. If this CL caused regressions, please revert and pause the autoroller at https://luci-scheduler.appspot.com/jobs/chrome/lacros-qa-qualified-tracking-roller Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org. R=rubber-stamper@appspot.gserviceaccount.com Change-Id: I49306ef745a9b2832277a0e6c9c61122d7b9de68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4381466 Auto-Submit: lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com <lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5672@{#113} Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd
pushed a commit
that referenced
this issue
May 27, 2023
Screen cap: https://drive.google.com/file/d/1Wstz1g5Iy7Piy6yRtp7mwfYUEqrRqrz4/view?usp=sharing&resourcekey=0-sx9SbFIy4B3-ftX220jP0w (cherry picked from commit a755d79) Bug: 1431377 Change-Id: Ic6cfb8701724c0abb49d53cea2476965722a60ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4406511 Reviewed-by: Anudeep Palanki <apalanki@google.com> Reviewed-by: Tomasz Wiszkowski <ender@google.com> Reviewed-by: Avi Drissman <avi@chromium.org> Commit-Queue: Jason Hu <hujasonx@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1136254} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4496870 Cr-Commit-Position: refs/branch-heads/5735@{#113} Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
blueboxd
pushed a commit
that referenced
this issue
Sep 10, 2023
Add the capability to call the Lens Web Standalone direct upload HTTP endpoint when uploading images to Lens via the NTP Lens upload dialog. - Added image processing library to downscale images before uploading to Lens for latency purposes. - Added finch flag to toggle between the existing upload path (scotty) and the newly added direct upload path. Change-Id: Id829bfd24ecc7c4604cf02f41b7023c269be40fe (cherry picked from commit b9f1df5) Bug: b/295021558 Change-Id: Id829bfd24ecc7c4604cf02f41b7023c269be40fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4749539 Commit-Queue: Joseph Lee <josephhlee@google.com> Reviewed-by: Roman Arora <romanarora@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1181614} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4778938 Reviewed-by: Moe Ahmadi <mahmadi@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5938@{#113} Cr-Branched-From: 2b50cb4-refs/heads/main@{#1181205}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been getting an increasing number of kernel panics on 10.9.5 (13F1911) and it's to the point of being intrusive. With version 107, sometimes I can go a day uninterrupted, and then others, like today, I had five. I've not been able to find any consistent cause – it's happened while loading pages, refreshing pages, scrolling pages, idling on pages, switching tabs, you name it. This wasn't an issue for me under older builds (104 and 105, specifically). It doesn't seem as though anyone else is having this issue, so feel free to let me know if it's potentially just something with my system. Also, I normally have some flags set, but this has happened even with them all set at their defaults. Lastly, I don't know if this is in any way related to Ublock Origin crashing (I'm sure it's not the extension's fault) because that also happens frequently (sometimes constantly), but sporadically – just that one, though, no others.
Logs
I'm including the most recent one, but they all list the same issue, just with a different last loaded kext.
The text was updated successfully, but these errors were encountered: