715692 - Strange content corruption after restoring session

Status: RESOLVED INCOMPLETE

(Firefox :: Session Restore, defect)

Description

[Mike Conley (:mconley) (:⚙️)]

Attachment: The corrupted content.

I can't seem to reproduce this one reliably, but periodically, after Firefox starts, if I go to a page that I've visited before, I see a bunch of garbage on the screen.  See attachment.

Shift-reloading seems to resolve it, so I think there's something fishy going on with the data in my cache.

Here's a list of my add-ons from about:support

  Extensions

        Name

        Version

        Enabled

        ID

        Add-on Compatibility Reporter
        1.0.2
        true
        [e-mail]

        Browser Sign In
        0.1.5
        true
        [e-mail]

        Bugzilla Tweaks
        1.11.3
        true
        jid0-qBnIpLfDFa4LpdrjhAC6vBqN20Q@jetpack

        DOM Inspector
        2.0.10
        true
        [e-mail]

        Mozilla Labs App Runtime
        0.5.1
        true
        [e-mail]

        Nicer Bugzilla Comments
        1.4
        true
        jid0-8OJNdDJ6MBHtfB9FElhQ3wt2FMw@jetpack

        NoScript
        2.2.5
        true
        {73a6fe31-595d-460b-a920-fcc0f8843232}

        Test Pilot
        1.2
        true
        [e-mail]

        Textarea Cache
        0.8.5
        true
        {578e7caa-210f-4967-a0d3-88fe5b59a39f}

        Visual Hashing
        0.2
        true
        jid1-NzIEzRc5sYX4Ww@jetpack

        Wallflower
        1.0
        true
        jid1-uB4sJEPvR2m4QQ@jetpack

Comment 1

[u279076]

Does this reproduce on a new profile?

Comment 2

[Mike Conley (:mconley) (:⚙️)]

I created a fresh profile and surfed around a bit, and I couldn't seem to reproduce it.

I'll just reinforce that I haven't found a reliable way of reproducing it on my default profile.  It just occurs from time to time.  :/

Comment 3

[u279076]

Could you slowly disable your add-ons one by one seeing if you can reproduce this.

Comment 4

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

That's certainly strange... my gut says that it's a corrupted cache. It almost looks like we loaded the content but with the wrong encoding. Maybe async cache writing resulted in an incomplete file? (do we even do async cache writing? it's text, so an incomplete file shouldn't look like that...)

Comment 5

[Mike Conley (:mconley) (:⚙️)]

So after a few days, I couldn't seem to reproduce this reliably. :/  Sorry!

Comment 6

[Wayne Mery (:wsmwk)]

Able to reproduce any more, at all?

Comment 7

[Mike Conley (:mconley) (:⚙️)]

Nope!