-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCC::SyncEngine::syncFileStatusTracker #11981
Comments
Observable for one year. Quite regular. Seems to start with 5.0 and still present in the latest release. Maybe worth a look. THX @erikjv |
Sometimes a `Folder` is created for a local path that we cannot sync (e.g. it's not writable). This folder will not have a sync engine. If the engine of this `Folder` is accessed, this will lead to a crash. The fix is to check for the existance of a sync engine in the `Folder::canSync()` method. Fixes: #11981
Sometimes a `Folder` is created for a local path that we cannot sync (e.g. it's not writable). This folder will not have a sync engine. If the engine of this `Folder` is accessed, this will lead to a crash. The fix is to check for the existance of a sync engine in the `Folder::canSync()` method. Fixes: #11981
Sometimes a `Folder` is created for a local path that we cannot sync (e.g. it's not writable). This folder will not have a sync engine. If the engine of this `Folder` is accessed, this will lead to a crash. The fix is to check for the existance of a sync engine in the `Folder::canSync()` method. Fixes: #11981
Sometimes a `Folder` is created for a local path that we cannot sync (e.g. it's not writable). This folder will not have a sync engine. If the engine of this `Folder` is accessed, this will lead to a crash. The fix is to check for the existance of a sync engine in the `Folder::canSync()` method. Fixes: #11981 Co-authored-by: Erik Verbruggen <[email protected]>
Can you provide the steps to test this fix. |
@erikjv can you answer this please? Thx |
@PrajwolAmatya I tried to reproduce it, but I can't. This fix was done by looking at the code and see what could possibly go wrong, and try to prevent that. So, no testing is needed. |
Sentry Issue: DESKTOP-WIN-AND-MAC-EPB
The text was updated successfully, but these errors were encountered: