Bugzilla

Hey Chris,
before clearing all the data stored for the app.slack.com domain, would you mind to check if you got something inside the `storage/default/https+++app.slack.com/cache/morgue/` directory in that profile?

I did notice that I had 1.7G morgue directory for app.slack.com, and even just renaming (or removing) the morgue directory but leaving it there did fix the issue in the test profile I'm using to keep triggering this issue as clearing all the data stored for app.slack.com, and I'd like to confirm if you also got something into the cache morgue directory.

I believe that may also be part of the side-effect of the actual underlying issue, but it may be part of the symptoms and may also help to get some ideas about what conditions may we getting us into that corrupted state.

Hey Chris,
before clearing all the data stored for the app.slack.com domain, would you mind to check if you got something inside the `storage/default/https+++app.slack.com/cache/morgue/` directory in that profile?

I did notice that I had 1.7G morgue directory for app.slack.com, and even just renaming the morgue directory but leaving it there (or removing) did fix the issue in the test profile I'm using to keep triggering this issue as clearing all the data stored for app.slack.com, and I'd like to confirm if other user affected have the cache morgue directory in a similar state (e.g. with an amount of data higher than usual).

I believe that may just be part of the side-effects of the actual underlying issue, but it may be part of the symptoms and may also help to get some ideas about what conditions may we getting us into that corrupted state.