Roboform Process Sometimes Causes Firefox to Hang/Stay Resident During Shutdown.

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
6 months ago
6 months ago

People

(Reporter: bugzilla, Unassigned)

Tracking

62 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 months ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180920131237

Steps to reproduce:

Running Roboform Version 8.5.4.4 (en-english, ENU) Sep 20 2018 10:45:46 with the Roboform Extension version 8.5.1.2.  I'm on Windows 7 Pro 64bit.

For the past several Firefox and Roboform versions, when closing Firefox it would either hang with a locked UI (version 60 and 61 at least) or stay resident in memory after UI went away (62).  

Using Task Manager to close the rf-chrome-nm-host.exe process allows Firefox to close and end the processes.  This is the process that seems to start when launching Firefox.

It doesn't always happen and I really haven't discerned any patterns to reproduce it.  It seems that it generates a number of Crash Reports for each process when this happens.  Latest one https://crash-stats.mozilla.com/report/index/79922309-7786-4e9a-8372-445d30180923

Note: This is my only password manager and I have all the built-in options disabled so Firefox itself doesn't save anything.


Actual results:

Firefox remain resident in memory after closing program.


Expected results:

Firefox should close normally.

Comment 1

6 months ago
I think this may be an Extension Compatibility-related issue so setting the component as such.

It may also have to do with possible admin settings on your OS. Are you running both Roboform and Mozilla Firefox as an administrator?
Component: Untriaged → Extension Compatibility
Flags: needinfo?(bugzilla)
(Reporter)

Comment 2

6 months ago
My Windows account is at the administrator level.  It hasn't happened again since I made the bug.  It's something that's not readily reproducible.
Flags: needinfo?(bugzilla)
You need to log in before you can comment on or make changes to this bug.