Comment 15 for bug 1652272

Revision history for this message
In , U552789 (u552789) wrote :

Oh dear, I am now awfully confused. I will have to do some more testing on this matter later on, maybe I will test it in Safe Mode for a longer time this time. For the issue has returned even though the Ghostery has been removed and GNotify disabled. When I closed the browser the same thing happened as before as well and I got this:

console.error:
  Message: Error: SessionFile is closed
  Stack:
    SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29
this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12
SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12
SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12
SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5
SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40
setTimeout_timer@resource://gre/modules/Timer.jsm:30:5

ExceptionHandler::GenerateDump cloned child 6768
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...