Tadly

No, by spike I actually mean that its load is at 90+% all the time (up until I kill it of course). Sorry for the confusion

Funny, forgot to close Enpass today at work and just got the spike again. Not sure who you PMed but I might be able to squeeze that in if you want (only via google hangouts or teamspeak though. Got my own teamspeak server) Just wanna mention again that this seems to be related to wonky network connections as I only get the spikes while at work, not at home.

Just for the log... Starting enpass from a terminal and leaving it in the background until the CPU spike happens, I end up with... ...flooding the terminal while enpass tries to sync (and never finishes) Hemant already knows about it and got some demo login-data to my webdav server. Let's hope that's of any help (:

Hi Hemant and thanks for your time. To answer some of your questions: Nope, no errors what so ever (I assume starting enpass from a terminal won't reveal any useful informations but I'll try anyway later on) As enpass is already trying to sync, I physically can not press the sync button myself as they are gone both within the settings and the normal UI If I open enpass, unlock it and sync myself it works just fine. Hm, interesting. However, renaming that directory causes sync not to work at all (even after re-configuring my sync settings) I'm not a Qt expert but I assume the bearer stuff is something network related meaning it's kinda obvious sync doesn't work anymore?

Hm. For whatever reason this happens way more frequently while connected to my offices wifi than when I'm at home. Might it be related to unstable network connections (like micro timeouts or whatever)?

Hm, as I'm using my own cert which doesn't expire in quite some time, I think there's more to that. Just saw there's a version bump to 5.2.1.1 Let's see if that fixes anything Edit: Nope, 5.2.1.1 doesn't fix that issue Oh and btw. this doesn't happen on windows (which I'm forced to use at work *shakes fist in anger*)

Alright, it's happening more frequently now (no idea why) and I'm pretty sure it's related to background syncing. As mentioned before, everytime the cpu spikes, enpass is trying to sync (and apparently fails doing so) Changing an entry and syncing manually works just fine. My setup than: Webdav server (I'm using wsgidav for that) behind apache2 with reverse proxy and a private wildcard ssl cert

Just wanna add that, for me, this doesn't happen right of the bat. Enpass can be running for a day or a day and a half and all of a sudden (while doing something completely different, not even using the browser) Enpass starts spiking up to 100% cpu load. I'll try and find a way to reproduce it but that's going to be difficult Edit: @Ankur Does enpass sync every now and than while in background? I noticed, while enpass was at 100% cpu load and re-opening it, it was syncing and didn't manage to "finish"

Thanks a lot for your investigation. That's strange. I'm not removing anything from the EnpassHelper as you can see here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=enpass-bin but after downloading and replacing the EnpassHelper binary, the extension works. Not sure how this can happen tbh. I assume this must be some problem with makepkg or something. I can only do some wild guessing at this point Anyway. Thanks again for helping us out here Edit: FOUND IT and I wasn't that far off with my wild guess. I can disable striping for packages which will be done by default and caused this issue. Thanks a lot you guys

Looks fine on my end $ lsof -i:10391 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Enpass 13246 tadly 17u IPv4 100556 0t0 TCP localhost.localdomain:10391 (LISTEN) Enpass 13246 tadly 22u IPv4 102837 0t0 TCP localhost.localdomain:10391->localhost.localdomain:54920 (ESTABLISHED) chrome 13459 tadly 223u IPv4 102836 0t0 TCP localhost.localdomain:54920->localhost.localdomain:10391 (ESTABLISHED) No output with the other ports Edit: lsof version is 4.89

OS: Archlinux DE: Gnome 3.20.1 (from the official arch repos) Error Message: There is none. At least none I consider related to the posted issue but following the output when starting enpass from terminal qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile QLayout: Attempting to add QLayout "" to QPasswordEdit "", which already has a layout

With Enpass 5.2 the browser extension stopped working (at least on chrome, don't know about FF or others as I don't use them) What I tried so far: 1. Reinstall the extension 2. Disable / Enable the browser extension support within Enpass -> Tools -> Settings What I discovered: Looking at the background.html of the extension while browser support is enabled all I see is Uncaught Error: Malformed UTF-8 data (That's fine as I have that on windows too and the extension works just fine). As soon as I disable browser support within Enpass, the js console screams errors about not being able to connect to the socket. This means, while browser support is enabled, the extension CAN connect to the Enpass socket (right?). Also, clicking the extension does NOT show the Enpass is not running page. Just nothing happens at all. Even the js console doesn't print/log anything.