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.

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

Twitter home page(latest) started regularly crashing "Error code: 5" in last week #22666

Open
gojomo opened this issue May 3, 2022 · 2 comments

Comments

@gojomo
Copy link

gojomo commented May 3, 2022

Description

Just in the last week, my usual, heavy use of Brave to read the Twitter main feed (https://twitter.com/home) has, after some time (at least tens-of-minutes) open, and scrolling down (triggering their progressive load), triggered a page crash, leaving me with the "Can't open this page" (sad tab) message.

After happening a few times, I tried the suggestion on the 'Learn more' help page of clearing all site-related data, and it has again recurred.

I've not noticed it on any other pages yet.

Merely rapidly down-scrolling until they won't load any more content is not enough to trigger, so time-open seems a factor. I don't think I've ver 'come back' to the page in the crashed state – rather, while it is the active tab, & I'm scrolling, down, the page is replaced with the error.

Steps to Reproduce

Visit Twitter's home page, logged-in. Over tens-of-minutes, scroll down, performing usual open-in-tab or like/reply/retweet actions. At some point, page content is replaced with error.

Actual result:

"Can't open this page" error, with "Error code: 5"

Expected result:

Page keeps working - as it reliably has for years until last <7d.

Reproduces how often:

Takes a while, but might happen every tme the page is left open long enough and gradually scrolled-down in normal use.

Brave version (brave://version info)

Brave 1.38.109 Chromium: 101.0.4951.41 (Official Build) (x86_64)
Revision 93c720db8323b3ec10d056025ab95c23a31997c9-refs/branch-heads/4951@{#904}
OS macOS Version 12.3.1 (Build 21E258)

Version/Channel Information:

  • Can you reproduce this issue with the current release?
  • Can you reproduce this issue with the beta channel?
  • Can you reproduce this issue with the nightly channel?

I can try on non-release channels if you think it's likely to fix.

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
    Will try soon.

  • Does the issue resolve itself when disabling Brave Rewards?
    Not currently enabled.

  • Is the issue reproducible on the latest version of Chrome?
    Switching back to Chrome for this Twitter-usage pattern now; will report back if it occurs (or doesn't after hours of use).

Miscellaneous Information:

Happy to enable & report any other deep bits of crash-debugging info, if you point me to instructions to collect.

@gojomo
Copy link
Author

gojomo commented May 3, 2022

Update: I've now received the same error in Chrome (Version 101.0.4951.41 (Official Build) (x86_64)).

And after updating Chrome, also in Chrome: Version 101.0.4951.54 (Official Build) (x86_64)

Highly likely a change in Chrome's engine and/or Twitter's JS in last week created crash conditions.

@gojomo
Copy link
Author

gojomo commented May 9, 2022

FYI: still happening in today's update, "Version 1.38.111 Chromium: 101.0.4951.54 (Official Build) (x86_64)"

Side observation: in this particular case – dealing with Twitter's infinite-scroll homepage – if the crash page retained a faded static image of the last renderable version of the page, it'd be a lot easier to get-back-to-where-I-was, after reload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant