Open Bug 1525020 Opened 2 years ago Updated 2 years ago

On Windows 10, losing the mouse cursor when I get a Firefox error page of any kind

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

defect

Tracking

()

UNCONFIRMED

People

(Reporter: jeff, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce:

On Windows 10, updated version of Firefox as of 2/4/2019

I get a page not found, or any other error page, and the windows cursor becomes blank and missing. I'm using a windows cursor that has mouse trails, and it has some transparent alpha pixels.

Actual results:

the windows pointer becomes blank and missing. I'm using a windows cursor that has mouse trails, and it has some transparent alpha pixels.

Expected results:

The cursor should not have changed.

I suspect that there was a call to change the cursor to a wait cursor, and then it failed.

If I sign out and sign back in, the cursor reappears.

The cursor doesn't change when I mouse over the browser.

On Comment 1, when you mention sign out and sign back in, do you mean with the Windows 10 OS or with some website/Firefox account?

Flags: needinfo?(jeff)

Moving from Untriaged to Core: Event Handling component. Please correct if this is not the case.

Component: Untriaged → Event Handling
Product: Firefox → Core

Hello,

I was logging out of Windows 10 and logging back in to get the cursor back.

I was able to get past the issue with a reboot.

After rebooting, I couldn't reproduce the problem.

It would seem to me that it's likely that there was a resource leak somewhere in the system, and maybe I was bumping up against the resource limit in Windows. That would explain the loss of the mouse cursor. I also had Chrome open, and the system uptime was over 20 days. I was using a proxy in Firefox. I also had recently opened a very large 100 MB web page.

You would have to get the system into a low-resource condition to reproduce. It would probably make sense to leave this ticket open for a while, in case I run into it again.

The version was v65.

Thanks!

Flags: needinfo?(jeff)
Priority: -- → P3
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.