Mouse cursor screwed up in a new way


#1

Fixed the previous bug, added a new one.

Go here: https://giphy.com/gifs/hug-entourage-Cyyw56DAmsoN2/links

Hover over Links > GIF Link (or any of the other similar links)

Now, try and copy or cut that link. No workee.

And it’s you, babe, not me. Not edge, brave, sriron, chrome, firefox or epic.


#2

Works just fine for me. which version are you running?


#3

Name
Version
Brave 0.21.24
V8 6.5.254.36
rev 19c78a1
Muon 4.9.3
OS Release 10.0.16299
Update Channel Release
OS Architecture ia32
OS Platform Microsoft Windows
Node.js 7.9.0
Brave Sync v1.4.2
libchromiumcontent 65.0.3325.162


#4

Mac OS X - Works - No Issues
Win 10 64 bit - Works - No Issues

I see our architectures are different… (ia32 vs x64)

Brave: 0.21.24
V8: 6.5.254.36
rev: 19c78a1624118e344852c4c0f44c0d45be841b5f
Muon: 4.9.3
OS Release: 10.0.16299
Update Channel: Release
OS Architecture: x64
OS Platform: Microsoft Windows
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 65.0.3325.162


#5

Have either of you been able to reproduce this error on a fresh tab / browser instance. There is a currently known bug(s) that affect open tabs and cause buttons, links, and other interactions to fail.

Right clicking the tab and “cloning” it will give you an exact copy of the tab but with the weird bug(s) fixed. Then you simply close the old one. If this isn’t the same bug, please give more accurate instructions on how to reproduce it, as the bug I’m thinking of is pretty random in it’s appearances.


#6

I’m seeing something similar, especially (but not exclusively) with Atlassian products. I click on a link and it does nothing. Or I click on a link or click in a textbox and its selects some random text/UI objects on the page (usually (always?) stuff that precedes the link or textbox in layout order).

Yes, I never see this in a fresh tab and yes, the clone tab workaround works for me.

Brave: 0.21.24
V8: 6.5.254.36
rev: 19c78a1624118e344852c4c0f44c0d45be841b5f
Muon: 4.9.3
OS Release: 10.0.16299
Update Channel: Release
OS Architecture: x64
OS Platform: Microsoft Windows
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 65.0.3325.162


#7

Hi All-

Seems to have solved itself, because of an unrelated reboot of windows. W10 has caused a series of minor weird problems in a number of programs.

Cheers,

Tom


#8

Could we get a response about what’s being done to solve this? It’s become a lot more frequent on my end recently and I’d like to at least have a way of collecting data for the team if my tabs are going to be crashing once every few hours. @eljuno? @LaurenWags?


#9

Reboot of windows 10.


#10

The problem is that I’ve had no series of minor weird problems in Windows 10. I’ll definitely restart soon, but I imagine the most this will do is delay the problem and I’d prefer if we were working towards solving it instead.


#11

Are you seeing associated crash reports in chrome://crashes when your tabs crash?

Lauren


#12

It looks like I do. What can I do with them other than sending them to google? Also it seems that Ctrl + Q counts as a crash as I just did it and have a report for each tab closed.


#13

If you are experiencing a crash each time you close Brave (that’s what it sounds like when you mention Ctrl +Q), we have an issue logged for that (not everyone experiences this): https://github.com/brave/browser-laptop/issues/12957

If you’re seeing only some tabs crashing, it would be helpful to know the “Uploaded Crash Report ID” which was generated at the time of the tab crash. The crash report ID which will look something like this d436c0a74d14858b - we don’t need the local crash ID. So after you see your tab crash, navigate to chrome://crashes. Send the crash reports (if not automatically sent). You can also post an issue on GitHub if you want (or here) with the relevant information (steps, brave version, OS info, etc).


#14

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.