Closed Bug 1196270 Opened 8 years ago Closed 7 years ago
Session restore, about:blank, injecting a script which calls alert(), Firefox either hangs or crashes
Asking for tracking-e10s? for the crash, hoping this attracts the right people who can comment on the other issue too.
I'm afraid I won't have time to look into this deeply for a while. Here is a possible workaround though. At the top of the frame script you could send a sync message to the parent process. The handler for that message could take message.target, which is a browser element, get the window utils from that, and then do the isParentWindowMainWidgetVisible check.
I couldn't reproduce this issue on: Version 46.0a2 20160205004003 User Agent Mozilla/5.0 (X11; Linux i686; rv:46.0) Gecko/20100101 Version 46.0a2 20160204004009 User Agent Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 The browser didn't crash, I got some console errors, but I think they're not realated: (firefox:14001): Gtk-WARNING **: GtkSocket 0x931f8c20 is mapped but visible=1 child_visible=1 parent MozContainer 0xa27fb3b0 mapped=0
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
I'm sorry, but the bug persists (everything is identical) :-/ Firefox Nightly 48.0a1 (2016-04-08) x32 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 Built from https://hg.mozilla.org/mozilla-central/rev/d9b1a9829c8ee2862955043f28183efa07de3d2b
Also tried on Linux: Firefox Nightly 48.0a1 (2016-04-08) x64 Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0 Built from https://hg.mozilla.org/mozilla-central/rev/d9b1a9829c8ee2862955043f28183efa07de3d2b Exactly the same problem.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Last bad: 50.0a1 (2016-07-25) Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Built from https://hg.mozilla.org/mozilla-central/rev/7c669d5d63efceb12696cd65cfa72c296013dafb First good: 50.0a1 (2016-07-26) Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Built from https://hg.mozilla.org/mozilla-central/rev/ff1ef8ec0fd800bf6856c1572c3b1610c45e9b6a Pushlog http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7c669d5d63efceb12696cd65cfa72c296013dafb&tochange=ff1ef8ec0fd800bf6856c1572c3b1610c45e9b6a The suspects are: https://bugzilla.mozilla.org/show_bug.cgi?id=1251841, https://bugzilla.mozilla.org/show_bug.cgi?id=1261842 and https://bugzilla.mozilla.org/show_bug.cgi?id=1278985.
trying to clarify comment 7 - does that mean it worked on that latest build you tried on 7/26... so this can be closed?
Yes, I think it may be closed. Anyone who has a different opinion please respond :-)
Flags: needinfo?(janekptacijarabaci) → needinfo?(arantius)
Status: REOPENED → RESOLVED
Closed: 8 years ago → 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.