Chrome multi-console extension issue related to browsing history
gs-scooter opened this issue · 2 comments
Describe the bug
The multi-console Chrome extension appears to be failing once I pass some kind of browsing history threshold. What happens is that at some random point, the desktop app will report communication errors with the browser/extension and operate in single-console mode. If I then go into the browser and clear all activity for the past month, then everything works fine.
Leapp Version
0.20.1
To Reproduce
Unfortunately, I cannot predictably reproduce since I don't know what the browsing history threshold is that triggers the behavior.
Expected behavior
Leapp connects with the browser extension successfully.
Desktop (please complete the following information):
- Windows
- 10
- Leapp Version 0.20.1
Additional context
Browser: Vivaldi
Thanks for reporting. This issue is much easier on Firefox due to the Firefox Container feature. Sadly it's not so easy to implement in Chromium-based Browsers.
Understood. FWIW, I was able to clarify today that it's a browser cache issue as opposed to browsing history.