Issue with cache on rollback (138 to 134) LInux

[edgardog]

Hello, I have a weird problem.
I have 3 different builds of CEF, #1 Branch 130 , #2 Branch 134 and #3 Branch 138 (the one I'm currently building).
The problem that I have is that if I run branch 138 and it writes to the cache , if I close it and run branch 134 (using the same cache folder) it fails to start. I narrowed down to a folder in the cache... cache/Default/Sync Data . If I wipe this branch 134 starts just fine.
I don't have the same problem when running first 138 and then running 130.. which is weird.
This Sync Data folder seems to have some LevelDB files. Maybe something changed on version 138 that makes it break on 134?

I can force it to delete this folder each time I close 138... so that would be a work around.. but I'm just curious if someone else had this problem and what is actually stored in there and if its safe to just wipe it every time I close 138.

[bjdupuis]

We noticed it when attempting to downgrade from M135 to M133. Without deleting the appropriate AppData on Mac OS it won't launch again.

[mbragg12]

I'm seeing the same issue on Windows switching between 137 and 135. App exits as soon as CEF starts to initialize.

[magreenblatt]

We've seen these kinds of issues before, where Chromium code does not support forward compatibility (e.g. running older version with newer cache crashes). These are generally considered bugs, and you can file an issue with Chromium at https://crbug.com/new. The fix will generally be with future versions (e.g. in the future they'll correctly delete/recreate the file if the format is unsupported).

[edgardog]

Thanks for the reply.
I'm currently wiping the cache/Default/Sync Data folder before running my current version (138) to avoid future problems, but I'm also wiping it on each time the app closes to allow rollback. This has worked so far... I don't wipe the whole cache.. just that Sync Data folder. I tried to figure out what is that being used for, but I could not... do you have any suggestions on where to look why that is there? (other than looking at the code). I would appreciate any pointers. If not, thanks for the suggestion.. I'll try to reproduce it on chromium and if it fails there as well I'll submit a bug.

[magreenblatt]

I would guess it’s for the Sync API. Details at https://www.chromium.org/developers/des ... ents/sync/

[bjdupuis]

Is there any way to disable the Sync API support?

[magreenblatt]

Is there any way to disable the Sync API support?

You can try "--disable-sync". I'm not sure if that will also stop the file from being created.

[magreenblatt]

For future reference, the crash is in WebAppDatabase::MigrateDatabase. It handles upgrade of older versions but crashes on newer versions (> 1).

[magreenblatt]

Is there any way to disable the Sync API support?

You can try "--disable-sync". I'm not sure if that will also stop the file from being created.

Doesn't help.