Extend local logging to cover session serialization and backup writing
Categories
(Firefox :: Session Restore, task, P2)
Tracking
()
People
(Reporter: sfoster, Unassigned)
References
(Blocks 4 open bugs)
Details
(Whiteboard: [fidefe-session-restore])
Bug 1854373 added a framework for local debug logging of session store operations, but it focused mostly on the startup flow and decisions and conditions encountered during the restore of a session. Clearly in many cases the interesting bit happens before the restart - when we update and serialize the browser state to the filesystem. We need to add more logging there to be able to understand how the end-state encountered during the next startup came to be.
|
Reporter | |
Updated•9 months ago
|
|
||
Updated•9 months ago
|
|
|
Reporter | |
Comment 1•17 days ago
|
||
When we set the crashReasons.FINAL_STATE_WRITING_INCOMPLETE we should log out any detail from that crash that the crash reporter has captured.
|
|
Reporter | |
Comment 2•17 days ago
|
||
(In reply to Sam Foster [:sfoster] (he/him) from comment #1)
When we set the
crashReasons.FINAL_STATE_WRITING_INCOMPLETEwe should log out any detail from that crash that the crash reporter has captured.
I filed bug 1950169 for this. The logging needs to happen at the next startup - which is a phase we have already instrumented.
Description
•