passman-webextension
passman-webextension copied to clipboard
nextcloud
Enabling Passman makes Chromium hang for a few seconds
In the last couple weeks, I've noticed that Chromium has been taking about 5-10 seconds to respond after it was launched. In troubleshooting it, I found that disabling Passman fixes the issue, so I'm filing this issue here.
Steps to reproduce
- Enable Passman Extension in Chromium
- Observe that Chromium hangs for 5-10 seconds
Expected behaviour
Passman loads with Chromium without taking a considerable amount of time.
Actual behaviour
Passman adds 5-10 seconds to the load time of Chromium.
Configuration
Operating system: Arch Linux
Browser: Chromium 62.0.3202.75
Extensions that might cause interference: uBlock Origin
Passman version: 2.1.4
Extension version: 2.0.4
Nextcloud version: 12.0.3
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Also you see the chromium window, but it's not responsive? How many vaults do you have added? How many credentials do you have?
Spec's of the pc you're running on would be nice.
It's a Lenovo P50 with a Xeon E3-1505M and 32 GiB of RAM.
Also you see the chromium window, but it's not responsive?
Yes, the Chromium window appears and hangs. Notably, on the new tab page after opening, the Passman icon badge shows a red box without text, and after the hang, it shows 0.
How many vaults do you have added?
Just one.
How many credentials do you have?
183 credentials.
Red icon during startup means it's connecting to the server. When you load the passman app, how long does it take to load the list?
Loading the app, as in the alpha Android application? When opening the vault, it only takes maybe 1/4 of a second or so.
I'm experiencing what might be the same issue. I can't speak to Firefox, but any time the Chrome extension is locked, Chrome (Google Chrome, not Chromium) experiences severe performance issues. CPU utilization is very low during this time.
To answer the questions posed to another user above:
- This is on two Macbooks, a 2014 with an i5 and 8GB RAM, and a newer one with an i7, 16GB RAM, and a Radeon R9 M370X. I haven't tried Windows or Linux.
- Chrome is visible but largely (not entirely) unresponsive.
- I've got one connected vault
- There are 30 credentials in the vault
If this seems like a separate issue, I can open another one.
Yea it's the waiting time (waiting for the server to respond) that makes the browser hang. Since it's also happening on the webapp.
FWIW, my issue is no longer occurring. I see that the only code changes since my comment seem to be in /_locales, but maybe a previous change that got pushed to the Chrome web store more recently or the recent Chrome update solved it.
Still present for me. I'm on Chromium 63.0.3239.108 and Passman extension 2.0.4 now.
This issue still has the "needs more information" label applied. What information can I provide?
This is now occurring for me again, in Chromium 79 on Linux. The browser is almost completely unresponsive until the master password is entered to unlock the vault. This time, it is pegging a CPU core. It's the main chromium process doing it, not one of the renderers or the GPU process.