All containers and data are reset after extension high cpu/memory consumption and crash. Backed up data are not respected. #2419
Comments
maxdevjs
changed the title
|
About the check with another synced device: everything seemed fine with the following versions: Firefox version: 102.0(64bit) On this device, the extensions so far does not cause high cpu/memory consumption and crash, but container rules are not respected anymore. Wondering if the second device began with issues after I enabled syncing for the crashing extension and/or if the issue affects extension version |
maxdevjs
changed the title
|
The data lost is caused by the action of disabling the extension. Sadly, this is a known bug that needs to be solved in Firefox itself. For the high cpu/memory consumption, if you can, it could really help to have a performance profile recorded. You can get more information on how to get one at https://profiler.firefox.com/. Finally, right after you open the browser after a crash, go to about:crashes (type it in the address bar) and see if there's a crash report. If yes, please share it here because it could contain valuable information to pinpoint the issue. |
|
@dannycolin thank you for the reply
|
|
Hey @maxdevjs, First of all, sorry for the very late response! If sync was enabled on multiple devices, it may be why you didn't loss your data. Or, maybe it didn't purge the data right away and you had the time to re-enable it before it happens. I'm not entirely sure how it works in the backend but I know that disabling/uninstalling the extension can easily lead to data lost (See bug 1549204) Where you running the profiler when the addon crashed or was consuming a lot of CPU/memory? AFAIK, it should definitely be captured by the profiler if it was the case. If it really doesn't show anything even when the problem occurs, I think it'd worth asking for more help on our chat platform at https://chat.mozilla.org especially in the #profiler:mozilla.org or #addons:mozilla.org rooms. Someone there is most likely more knowledgeable than me on how to debug this type of problem. You can find more information on how to connect to our chat platform at https://wiki.mozilla.org/Matrix. |
|
@dannycolin thank you for the reply.
Yes, I lost the data. Only the containers names (I do not know what more, if) were restored. The data was lost (no site opened in the right container, etc) As an aside, I previously disabled/enabled several times the extension for the same kind of issue without data loss (as said).
It happens that on the other device, after the crash/data loss) the containers were "scrambled": a mix of my current (at the time) containers with old (deleted many months ago) containers. I wonder if it is actually more a backend issue.
My capture was not during the crash, sorry. I posted it because the extension was enabled, but after the data loss.
This would be interesting. I am not using the extension anymore (and I do not plan to use it in future, unless it's for simple debug purpose), but I am curious about what happened. |
Before submitting a bug report
Step to reproduce
1."random" high extension memory consumption
2. extension crash
Actual behavior
Firefox version: 105.1(64bit)
Extension version: 8.0.7
Firefox version: 102.0(64bit)
Extension version: 8.0.7
Issue:
container.jsonwas resetcontainer.jsonisnotstored in the Firefox profile directorywrong: a mix of early (no more existing in any other device) and recently createdEnable Syncis disabled/enabled every timeI found a few issues #1968 #2400 #2411 ... reporting about data loss.
Expected behavior
The extension should behave normally.
Additional informations
Even if high cpu/memory consumption and crash already happened previously, this is the first time that I experience data loss.
Provide a copy of Troubleshooting Information page (optional)
The text was updated successfully, but these errors were encountered: