Typing too fast when using search via browser extension menu gives erroneous result
When pressing ALT + backslash in e.g. Chrome and typing to search for an account it sometimes misses several letters when building the search result. E.g. typing in 'cloud ' searches for 'clod' thus not displaying what I wanted to look for.
It seems this problem is getting worse when I get more and more logins, currently I have 134 Logins and still increasing. I guess the extension or 1Password cannot keep up with the typing rate because it is still searching and building results. Maybe caching in memory also has to do something with it because the second, third, etc time it can keep up with my typing for the same word.
Comments
-
It also has something to do with decrypting your data/information on the fly. However this has a lot to do with the performance of your machine.
For example: I run a Windows 8.1 virtual machine off of a very fast USB3.0 flash drive quite often for testing. There, and on PCs with harddrives, I sometimes experience this issue. Running Windows 8.1 on a SSD-equipped, regular PC, this never occurs for me.
I hope this helps!
0 -
It also has something to do with decrypting your data/information on the fly. However this has a lot to do with the performance of your machine.
With the agilekeychain format, as I understand it, the title and url are unencrypted so why would there be a decryption related delay. For opvault it would be understandable but not for agilekeychain.
0 -
That is correct Richard, in the case of an .agilekeychain it's most likely related to the responsive of the UI on the user's machine.
0 -
With the agilekeychain format, as I understand it, the title and url are unencrypted so why would there be a decryption related delay.
@RichardPayne Multiple URLs are encrypted. We do not decrypt them unless "Lenient URL matching" is ON.
@admxnl Here is something you can try:
- Start 1Password
- Unlock
- Turn ON this setting: Help > Advanced > Tune 1Password for max performance
0 -
I've noticed this disables 'Lenient URL matching', maybe this has to do something with this delay?
I remember I needed to enable this option to match some URL's but will test for a while with this disabled.
0 -
@svondutch frankly, this is just an example of why the current search implementation is a bit of a kludge. The search retrieval code should not be running on the UI thread.
0 -
Found my previous post about 'Lenient URL matching', this gave problems for some logins with subdomains. Enabling this option solved this problem for us. I will still try without this option to see if performance improves.
0