Performance Issues
Extension crashes or extension settings resetting to default are frequently caused by
security products, such as Endpoint Detection and Response (EDR) or Antivirus tools,
interfering with the browser's local file operations.
Symptoms: - Extension crashes
- Extension crashes resetting to default
- Extension deployment failures due to an environmental block restricting
write access to the local profile
- Tab crashes potentially caused by an extension
Potential Cause (Troubleshooting Focus)
EDR or similar tools are scanning the extension storage paths within the user
profile, which can block necessary read or write operations. The user profile
directories (which contain configurations, caches, and databases) have very high I/O
and can be strongly impacted if heavily scanned.
Resolution / Mitigation
- Evaluate excluding the extension storage paths from EDR scanning for
improved performance and stability.
- If an environmental block is restricting write access to the local profile
directory (%LOCALAPPDATA% on Windows), consider:
- Removing the EDR/environment block.
- Using the --user-data-dir flag to redirect the
browser to a directory with guaranteed write permissions.
Troubleshooting Version and Profile Integrity Issues
Issues related to the browser version or session integrity can prevent successful
launch or operation.
| Symptom | Root Cause | Action/Notes |
| Startup failure on clean installation | A critical issue in a specific browser version can affect
fresh (not previously installed) installations. | This requires deploying gradually and having an earlier log
service. |
| Browser re-login or user profile loss | An environmental issue is preventing the browser from
verifying its internal engine, leading to a session failure or
re-login. | This requires addressing the environmental read block
preventing engine verification. |
| Silent auto-update failure or installer blockages | Active security products (EDR/Antivirus) are blocking the
installer or updater executables. | Refer to EDR Exclusion guidelines for updater paths. When
allowing executables like updater.exe, you may
need to use a parent directory rule or *
to target all versions, as the <VERSION>
component in the path changes with updates. |