Performance issue with web applications when Bitwarden browser extension is enabled

Ask the Community Password Manager
, ,
1

Dear Community!

We are using the browser extension with Edge and Firefox.

From beginning we faced a performance slowdown during the work in more then one web application. When we close the tab and restart the web session the performance is fine for a while again. After couple of minutes / hours it slows down again.

But when the Bitwarden browser extension is not enabled, there is absolutely no performance issue. The web application works as aspect (tested with three different web apps).

So there is definitely a relation between the performance and the Bitwarden browser extension.

Has anybody faced this too and/or has anybody an idea how we can fix this?

Thank you in advance.

Best regards from Germany

Sebastian

2

@sebgru Welcome to the forum!

And Sorry for the delay…

There is a comment in a GitHub issue that lists some open (and closed) GitHub issues that might be about the same thing you experience: Severe input lag (typing delay) in Firefox on Linux with Intel Graphics · Issue #18187 · bitwarden/clients · GitHub

Explanation: GitHub is the place for reporting bugs.

If one of those existing GitHub issues matches, you can add your details there. – And if none of those matches, you can open a new issue there.

3

Hello Nail,

hello @all,

I would like to tell you, that we have no solution until now. But I have a workaround :

I’ve added the WebApp URLs to the “block autofill Domain”. With that the performance is as aspec t.

Now I search for an option to deploy that URLs to all clients …..

BG

Sebastian

4

Did you join (or open) any issue on GitHub? – Or contact BW support?

5

Yes I did. But no solution. They can’t reproduce the issue. It seems to be a multiparameter problem between the WebApps and the Bitwarden Addin…

Here is the Github post: Performance degradation over time in web applications when extension is enabled (Edge & Firefox) · Issue #18771 · bitwarden/clients

6

At least it wasn’t closed as not reproducible, but it’s still open…