-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Vertical Tabs Crash #29398
Vertical Tabs Crash #29398
Comments
@Comprehensive-Jason Do you see a report in brave://crashes? Can you send and post the crash id here. |
cc: @sangwoo108 |
@rebron This is what I got: Crash from Wednesday, March 29, 2023 at 7:48:17 PM |
Uploaded: Crash from Wednesday, March 29, 2023 at 7:48:17 PM |
Thank you so much for reporting. Looks like this one
|
@Comprehensive-Jason , Sorry but I wasn't able to reproduce this bug on my Win10/11. Could you tell me more about your tabs? Do you have pinned tabs or groups? If so, how many are they? And also I'm wondering if this happens when you have a single new tab. |
@simonhong @petemill @fallaciousreasoning , could you help me with this? Honestly, I have no idea about what can cause this in the call stack. |
Interesting - I can't reproduce either (not in a new profile, not in my existing Nightly). The stacktrace doesn't look particularly helpful either - do you think it could be hitting the I did encounter a similar (ish) issue a while back on Linux, where the browser would crash when creating a new window with vertical tabs enabled but it seems different enough that it could be unrelated. @Comprehensive-Jason do you mind trying the even more drastic step of (temporarily) deleting your Nightly profile?
To get back your old profile:
|
Yeah, sounds possible. I'll try adjusting DPI on my machine. |
Oh, I adjusted dpi to 175% and it crashed. @Comprehensive-Jason Could you checkout your DPI? I guess it might be okay with 150% or 200%. Meanwhile, I'll try fixing it. |
@fallaciousreasoning I tried your suggestion. The crash still occurs. @sangwoo108 I changed Windows scale to 300% from my default 125% and clicked on |
300%, thanks! Will chekc that too |
@sangwoo108 After changing back to 125%, it now crashes immediately on startup, and I can't open it at all. |
100% might save you to open it, otherwise, I think we should modify pref manually. |
100, 150 percent work. 125,175 percent don't work. |
Thanks for checking! Will make a patch asap. Thanks @fallaciousreasoning , That was a huge help! |
The above requires |
Verification
|
Brave | 1.51.86 Chromium: 112.0.5615.49 (Official Build) beta (64-bit) |
---|---|
Revision | bd2a7bcb881c11e8cfe3078709382934e3916914-refs/branch-heads/5615@{#936} |
OS | Windows 10 Version 22H2 (Build 19045.2846) |
First, reproduced original crash using 1.52.2
:
Steps:
- on
Windows 10
, opened theDisplay
control-panel applet - chose
175% / 125%
(see screenshot, above) forScale and layout
/Custom scaling
values - launched Brave
- loaded a few sites
- context-clicked on the tab's title
- chose
Use vertical tabs
Crashed, in (sample incident ID of 2d380200-cefb-e309-0000-000000000000):
[ 00 ] `anonymous namespace'::BraveVerticalTabStyle::GetPath(TabStyle::PathType,float,bool,PathType::RenderUnits) ( brave_tab_style_views.inc.cc:154 )
[ 01 ] _tailMerge_esent.dll
[ 02 ] _tailMerge_esent.dll
[ 03 ] static void `anonymous namespace'::GM2TabStyle::PaintTabBackground(class gfx::Canvas *, TabActive, class absl::optional<int>, int) ( tab_style_views.cc:823 )
[ 04 ] static void * allocator_shim::internal::PartitionMalloc(const struct allocator_shim::AllocatorDispatch *, unsigned __int64, void *) ( allocator_shim_default_dispatch_to_partition_alloc.cc:302 )
[ 05 ] _tailMerge_esent.dll
[ 06 ] ThemeServiceFactory::GetBrowserContextToUse(content::BrowserContext *) ( theme_service_factory.cc:27 )
[ 07 ] _tailMerge_esent.dll
[ 08 ] _tailMerge_esent.dll
[ 09 ] malloc ( allocator_shim_override_ucrt_symbols_win.h:71 )
[ 10 ] Profile::IsTor() ( profile.cc:24 )
[ 11 ] profile_metrics::GetBrowserProfileType(base::SupportsUserData const *) ( browser_profile_type.cc:47 )
[ 12 ] `anonymous namespace'::GM2TabStyle::PaintTab(gfx::Canvas *) ( tab_style_views.cc:515 )
[ 13 ] _tailMerge_esent.dll
[ 14 ] `anonymous namespace'::BraveVerticalTabStyle::PaintTab(gfx::Canvas *) ( brave_tab_style_views.inc.cc:171 )
[ 15 ] views::View::Paint(views::PaintInfo const &) ( view.cc:1243 )
[ 16 ] void GlyphTrackingDevice::~GlyphTrackingDevice() ( SkChromeRemoteGlyphCache.cpp:642 )
[ 17 ] _tailMerge_esent.dll
[ 18 ] _tailMerge_esent.dll
[ 19 ] _tailMerge_esent.dll
[ 20 ] _tailMerge_esent.dll
example | example | example |
---|---|---|
Confirmed FIXED using 1.51.86
:
Steps:
- on
Windows 10
, opened theDisplay
control-panel applet - chose
175% / 125%
(see screenshot, above) forScale and layout
/Custom scaling
values - launched Brave
- loaded a few sites
- context-clicked on the tab's title
- chose
Use vertical tabs
- confirmed no crash
- shut down and relaunched
- confirmed no crash
- drag & dropped tabs
- confirmed no crash
example | example | example | example |
---|---|---|---|
Description
Brave Nightly crashes as soon as vertical tabs are enabled.
Steps to Reproduce
Actual result:
Brave Nightly immediately crashes
Expected result:
Brave should not crash and vertical tabs should work as they have been in previous releases.
Reproduces how often:
Easily reproduced, occurs every time
Brave version (brave://version info)
Version/Channel Information:
No, vertical tabs aren't rolled out yet.
N/A, don't use.
Update from @sangwoo108 - looks like it happens on Nightly - changed to 125%
Yes, every time.
Other Additional Information:
No.
No.
No, vertical tabs aren't available on Chrome.
Miscellaneous Information:
This issue just started occurring 1 day ago.
The text was updated successfully, but these errors were encountered: