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

Chromium Legacy crashing on different machines on OS X Lion 10.7.5 #41

Closed
ghost opened this issue Dec 7, 2021 · 9 comments
Closed

Chromium Legacy crashing on different machines on OS X Lion 10.7.5 #41

ghost opened this issue Dec 7, 2021 · 9 comments

Comments

@ghost
Copy link

ghost commented Dec 7, 2021

Hello!

Today me and my friend encountered an issue, trying to run Chromium Legacy on macOS Lion 10.7.5

Running in results in a minute of visual glitches, and then it crashes.

IMG_1604
20211207_112440

Both crash logs have mentions of issues like EXC_BREAKPOINT (SIGTRAP) and IntentionallyCrashBrowserForUnusableGPUProcess

I can share the crash logs if needed.

What is the issue?
@Wowfunhappy
Copy link

Wowfunhappy commented Dec 7, 2021 •
edited
Loading

Have you installed Lion Security Update 2014-004? If you haven't, please do so and try again. :)

(I find it really odd that even the macOS security dialog is garbled...)

@ghost
Copy link
Author

ghost commented Dec 7, 2021

Yeah, both machines are on the newest version there is.

@Wowfunhappy
Copy link

Wowfunhappy commented Dec 7, 2021 •
edited
Loading

Yeah, both machines are on the newest version there is.

I hope I'm not being annoying, but just to make absolutely, positively sure we're on the same page—the security update I linked to will not actually change the OS version or build number. What happens if you attempt to download and install that update from Apple's site?

Sorry, it's just, the problem you're describing is exactly what I'd expect to happen if 2014-004 wasn't installed, including the mention of IntentionallyCrashBrowserForUnusableGPUProcess, so I'm suspicious!

If that's really not it, definitely do post the full crash log, it may be helpful for Bluebox. And, can you try a slightly older release (perhaps 944367 from two weeks ago) to see if the break happened recently?

@ghost
Copy link
Author

ghost commented Dec 7, 2021

I tried many different versions, including one from May. Nothing worked. I'll try and see, but I'm almost positive the update is installed.

If it is, I'll post the logs.

@blueboxd
Copy link
Owner

blueboxd commented Dec 7, 2021

@Wowfunhappy Thank you for your help as always!

@fireinghex Hi!
Your renderer process is not usable (maybe died at startup) for some reason.
Do you have a crash log of Chromium Helper (Renderer)?
And are there any log entries (not crash log) in Console.app -> All Messages?
(try filtering with Chromium)

@pjpreilly
Copy link

pjpreilly commented Dec 7, 2021 •
edited
Loading

I deleted Safari and I'm getting this error message from chromium helper does chromium helper need the Safari app? I have a chromium helper crash attached.

12/7/21 10:01:43.392 AM Chromium Helper (Renderer): Error -10811 retgisting path /Applications/Safari.app
12/7/21 10:02:38.369 AM [0x0-0x14014].org.chromium.Chromium: objc[341]: Object 0x10a350f20 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
Chromium Helper (GPU)_2021-12-07-031604_Alliess-MacBook.crash.zip

@pjpreilly
Copy link

Also I find that I cannot get any graphics until I open up task manager and proceed to kill the GPU process it reloads I get graphics

@blueboxd
Copy link
Owner

blueboxd commented Dec 7, 2021

@pjpreilly

Error -10811 retgisting path

Means nothing, not related to crash.
And your case is another problem, please open new issue.

@ghost
Copy link
Author

ghost commented Dec 7, 2021

Apologies, that update fixes it. Thank you for the information!

@ghost ghost closed this as completed Dec 7, 2021
blueboxd pushed a commit that referenced this issue Feb 3, 2022
@naskooskov
[M98] Convert DCHECK to CHECK in Bookmark Manager
8f92f21 
This CL converts a DCHECK into a more stringent CHECK to ensure we crash
the browser process instead of hitting a use-after-free condition.

(cherry picked from commit 7c66fad)

Bug: 1249426
Change-Id: I919bfc4dcd11b8acccf217f5000fe7f1fbec7e6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3323662
Reviewed-by: John Lee <johntlee@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Nasko Oskov <nasko@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#950388}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3339653
Auto-Submit: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/branch-heads/4758@{#41}
Cr-Branched-From: 4a2cf4b-refs/heads/main@{#950365}
blueboxd pushed a commit that referenced this issue Jun 22, 2022
[iOS] Redirecting to Passwords UI when opening a specified link
42aa649 
This change redirects users to Passwords UI and cancels request when opening https://passwords.google.com/native

More details can be found here: https://docs.google.com/document/d/1YoV7Na2zX5_0IDtZqlGsKCkiFNoBs-EkVulTHEXWBUM/edit#

(cherry picked from commit b53742b)

Bug: 1324293
Change-Id: I52a2f77b58dfb31d0a6a8c1c8bc25f2fe796ec26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3645207
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1003202}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3645418
Cr-Commit-Position: refs/branch-heads/5060@{#41}
Cr-Branched-From: b83393d-refs/heads/main@{#1002911}
blueboxd pushed a commit that referenced this issue Aug 31, 2022
Update Crashpad to 1b47570f6f4192f3effa9976529c9b81f66b06f0
dffc438 
fab4801e1e88 [fuchsia] Fix ubsan issues
1b47570f6f41 ios: Add buffered write to IOSIntermediateDumpWriter

(cherry picked from commit 19193e0)

Bug: 1347204
Change-Id: I1bd2004346276e3a97d68718a80399d4cbede9c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3783712
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1027739}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3788296
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Harry Souders <harrysouders@google.com>
Owners-Override: Harry Souders <harrysouders@google.com>
Reviewed-by: Harry Souders <harrysouders@google.com>
Cr-Commit-Position: refs/branch-heads/5195@{#41}
Cr-Branched-From: 7aa3f07-refs/heads/main@{#1027018}
blueboxd pushed a commit that referenced this issue Sep 29, 2022
Switch V8 reference to git hash
9193311 
Bug: 1341211
Change-Id: Ia6e8f25e90270f5e4ff86123e224af1c40aded44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3849976
Reviewed-by: Lutz Vahl <vahl@chromium.org>
Commit-Queue: Liviu Rau <liviurau@chromium.org>
Reviewed-by: Michael Achenbach <machenbach@chromium.org>
Auto-Submit: Liviu Rau <liviurau@chromium.org>
Cr-Commit-Position: refs/branch-heads/5249@{#41}
Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
blueboxd pushed a commit that referenced this issue Nov 30, 2022
[M108 merge] WebUI tab strip: fix tab not able to drag out of tab group
95e9608 
This CL fixes a regression bug recently introduced by [1].
Now shouldPreventDrag() will take a boolean to indicate user is dragging
a tab or a tab group in order to handle separately.

[1]https://chromium-review.googlesource.com/c/chromium/src/+/3789615

(cherry picked from commit 364fcda)

Bug: 1369915
Change-Id: Ia14e1fe3ecbaa6e2552b31e75eac1d864713d12b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3947689
Commit-Queue: Yuheng Huang <yuhengh@chromium.org>
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1059388}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3960532
Cr-Commit-Position: refs/branch-heads/5359@{#41}
Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
blueboxd pushed a commit that referenced this issue Feb 8, 2023
@ben-reich
[M110] [FilesTrash] Fix shouldMoveToTrash from false positives
070bb76 
The shouldMoveToTrash was added at CL:4022743 to clean up some existing
tech debt. Unfortunately the logic didn't exactly mimic the existing
one. This instead ensures that an entry is verified against all Trash
volumes and their paths before returning.

Further to this, an additional test is added to ensure the failure case
doesn't regress and the tests bolstered to ensure when the delete button
is pressed the move to trash button is not visible (the inverse is
already verified).

(cherry picked from commit 869375c)

Bug: b:263297230
Test: browser_tests --gtest_filter=*trash*
Test: Deploy to DUT and verify
Change-Id: Id91fe82265a26768c74c48842c231eee664d04f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4119624
Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Ben Reich <benreich@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1085798}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4119985
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/branch-heads/5481@{#41}
Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
blueboxd pushed a commit that referenced this issue Mar 7, 2023
[M111] blink: two changes for html fast path parser
b558a77 
1. this tightens the restriction around failing if
   Document::IsDirAttributeDirty is set to also check if
   css-pseudo-dir is enbled. This restriction is in place because
   the fast path doesn't call to BeginParsingChildren(). AFAICT the
   only time the function needs to be called is if css-pseudo-dir is
   enabled. It should be possible to make the fast path work with
   css-pseudo-dir, but I'm going to hold off on that as
   css-pseudo-dir is experimental and we get more data on the
   fast path.
2. changes logging of times to only log on devices with high resolution
   accuracy as well as changing the buckets. Early data shows parsing is
   generally less than < 1 ms, even at the 99%, which means we should be
   logging at microsecond accuracy.

(cherry picked from commit 48a0d66)

Bug: 1407201
Change-Id: Ibc9afe151753078f22f0bc7069cafa443e4c58f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4198237
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1097723}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205009
Cr-Commit-Position: refs/branch-heads/5563@{#41}
Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
blueboxd pushed a commit that referenced this issue Apr 14, 2023
[m112][omnibox][ui-simplification] Truncate answers to 1 line.
ce433c3 
m112 merge CL. Original CL: crrev.com/c/4288114

2-line answers look weird with 1-line entities. This CL truncates them
to 1 line.

A future CL will drop the pronounciation text from dictionary answers to
leave more room for the actual definitions.

Before/after <todo>

(cherry picked from commit 46e2cfe)

Bug: 1368852
Change-Id: Idae2f4236dfa5be4994b1f0585d55204c927e695
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4288114
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1109239}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296070
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: manuk hovanesian <manukh@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5615@{#41}
Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd pushed a commit that referenced this issue May 9, 2023
[iOS] Add more information for DCHECK in SigninPromoViewMediator
3efd48b 
Implement -[SigninPromoViewMediator description] to display useful
information.
And add this description each DCHECK of this class.

This should help to understand http://crbug.com/1427347.

(cherry picked from commit f002edb)

Fixed: 1427612
Bug: 1427347
Change-Id: I844fe46f3dd1470993efafcf4d7d993d181a6fdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4369967
Auto-Submit: Jérôme Lebel <jlebel@chromium.org>
Commit-Queue: Tina Wang <tinazwang@chromium.org>
Reviewed-by: Tina Wang <tinazwang@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1121927}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4372284
Cr-Commit-Position: refs/branch-heads/5672@{#41}
Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd pushed a commit that referenced this issue May 27, 2023
[lacros skew tests] Refresh skew tests for M115 M113
2a14663 
This CL updates the ash version ['115.0.5737.0', '113.0.5672.67'] for Lacros version skew testing.
This cl only affect linux-lacros config builders like
linux-lacros-tester-rel, linux-lacros-rel.
This cl will certainly NOT affect Lacros on-device builders
(lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab,
etc) or any other platforms.

If this CL caused regressions, please revert and stop the autoroller
at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller
Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Bug: None
Change-Id: I248fbf07e8f082c98fe4c2d6671f4e6ad2d5b926
Requires-Testing: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4486257
Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@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/5735@{#41}
Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

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