-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
Crash Report #44196
Comments
I uploaded two other crash reports, one from earlier today 53c81700-b339-6c0d-0000-000000000000 and one from yesterday 23d21700-b339-6c0d-0000-000000000000. Before these three crashes, my last crash was 3 months ago. |
Thanks for reporting, @robhull! Seems to be related to drag and drop- will need to dig in more. Both crashes in your last post seem to have the same call stack. Employees can see this with the following link:
|
cc: @iefremov @atuchin-m |
I see 126 crashes during last 90 days (it's not so bad). The crash is likely to be trigged by drag-and-drop. It's probably an upstream issue started with cr133. Also there are few hangs with the same callstack: https://share.backtrace.io/api/share/TMTx2SlKVjRWV6afyYe6EV2 |
There is a recent upstream fix: https://chromium-review.googlesource.com/c/chromium/src/+/6190427 @iefremov Do you think it make sense to cherry-pick it before upstream? (just the one line fix, not the test) |
Confirmed. I just tried to drag an image from a browser window to a folder on my desktop and it crashed again. |
given the amount of crashes i'd say we just wait for the upstream to fix |
I don't have visibility to issue; it's restricted as @atuchin-m shared. But I asked in the CL if they can create a merge request for M134. We can assign this issue to the appropriate milestone (ex: if fixed in 134 we can tie to 1.76, fixed in 135 assign to 1.77, etc) |
@iefremov @atuchin-m Same issue causing -> #44312 |
@rebron Anyway if you feel that we should backport the fix, let's do it. |
IMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it.
Brave Version: 1.75.180 Chromium: 133.0.6943.126
Operating System: Windows NT 10.0.22631
URL (if applicable) where crash occurred: https://playscrabble.com/
Can you reproduce this crash? No. Brave has just started crashing randomly over the past few days. It just quits, no message or anything, just suddenly closes. Brave has been very stable for years for me, with approx the same extensions installed and lots of tabs open. I haven't changed anything recently apart from the usual Brave upgrades.
What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?)
DO NOT CHANGE BELOW THIS LINE
Crash ID: crash/5bc81700-b339-6c0d-0000-000000000000
The text was updated successfully, but these errors were encountered: