Chrome on Linux "frezes" at extension activation

[Marco-Jacobs]

Steps to reproduce

1. Install the Chrome Extension

Actual behaviour

The moment the extension gets activated the browser nearly is frozen. If you invest a few minutes to disable the plugin, that moment you disable it, the browser will instantly run as it should. I tested it a few times. And as far as i can say, it seems there must be a website open to reproduce. And while the plugin is active chrome uses 100% of one cpu core.

All other clients (Windows/Android) are working fine. But since an Update i dont know on wich (chrome or passman), this behavior exist.

Configuration

Operating system: Manjaro / Arch Linux 18.1.0 Browser: Chrome Version 77.0.3865.90

Passman version: 16.0.5 Extension version: 2.1.2 Nextcloud version: 2.3.2

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/81421866-chrome-on-linux-frezes-at-extension-activation?utm_campaign=plugin&utm_content=tracker%2F52236699&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F52236699&utm_medium=issues&utm_source=github).

[brainchild0]

Confirmed that single chromium process uses all cycles on a core and that all browser windows become completely unresponsive.

Known solution is to terminate browser forcibly, restart in safe (incognito) mode, then disable extension.

---

Linux Mint 19.04 Chromium Browser 77.0.3865.90 Passman Chrome Extension: 2.1.1

[kingcc]

Same Issue.

Extension source: Chrome WebStore Operating system: Arch Linux 4.19.69-1-lts Browser: Chrome Version 77.0.3865.90

[Werebear77]

Some problem.

Gentoo Linux Chromium 83.0.4103.61 Passman Chrome Extension: 2.1.2

On Windows work fine.

[mickare]

The project is dead!? :o

One year later it still makes Chromium unusable.

Arch Linux OS: 5.8.6-1-MANJARO Browser: Version 85.0.4183.102 (Official Build) Arch Linux (64-bit)