You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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)
Version/Channel Information:
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.
The text was updated successfully, but these errors were encountered: