Closed Bug 1123462 Opened 9 years ago Closed 8 years ago

All pages are blank with E10S enabled

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: u521557, Assigned: handyman)

References

Details

(Keywords: regression, Whiteboard: [gfx-noted]) 

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150108202552

Steps to reproduce:

I run Firefox with both hardware acceleration and E10S enabled.


Actual results:

Every page were displayed blank.


Expected results:

Pages should be displayed normally.
You tried to use e10s on Firefox 35? I don't think we support that; try running it on Nightly instead. If you *are* running it on Nightly, can you post your about:support graphics information? And, did this used to work and did it recently break, or is this the first time you tried?
Flags: needinfo?(silvuss)
I have run it on Nightly. I have tried it a few times, from (day before yesterday?) update it never worked.
But now I noticed that some sites are displayed correctly for a moment, then they become blank.

This is my about:support :



Application Basics
------------------

Name: Firefox
Version: 38.0a1
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0
Multiprocess Windows: 1/1

Crash Reports for the Last 3 Days
---------------------------------

Report ID: bp-557f8208-faa3-47c2-a51a-038192150119
Submitted: 38 minutes ago

All Crash Reports (including 1 pending crash in the given time range)

Extensions
----------

Name: Bytemobile Optimization Client
Version: 4.2.2
Enabled: false
ID: ff-bmboc@bytemobile.com

Graphics
--------

Adapter Description: Intel(R) Graphics Media Accelerator 3600 Series
Adapter Drivers: igdumd32
Adapter RAM: Unknown
Device ID: 0x0be1
Direct2D Enabled: Blocked for your graphics driver version.
DirectWrite Enabled: false (6.2.9200.16571)
Driver Date: 2-27-2012
Driver Version: 8.14.8.1075
GPU #2 Active: false
GPU Accelerated Windows: 0/1 Basic (OMTC) Blocked for your graphics driver version.
Subsys ID: 061f1025
Vendor ID: 0x8086
WebGL Renderer: Blocked for your graphics driver version.
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Important Modified Preferences
------------------------------

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 286720
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 1
browser.places.smartBookmarksVersion: 7
browser.sessionstore.upgradeBackup.latestBuildID: 20150119030222
browser.startup.homepage: about:home
browser.startup.homepage_override.buildID: 20150119030222
browser.startup.homepage_override.mstone: 38.0a1
browser.tabs.remote.autostart: true
browser.tabs.remote.autostart.1: false
dom.mozApps.used: true
extensions.lastAppVersion: 38.0a1
font.internaluseonly.changed: false
media.gmp-gmpopenh264.lastUpdate: 1416647048
media.gmp-gmpopenh264.version: 1.1
media.gmp-manager.lastCheck: 1421698643
network.cookie.prefsMigrated: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1421698644
places.history.expiration.transient_current_max_pages: 27431
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.importedState: true
print.print_bgcolor: false
print.print_bgimages: false
print.print_colorspace:
print.print_command:
print.print_downloadfonts: false
print.print_duplex: 1515870810
print.print_evenpages: true
print.print_in_color: true
print.print_margin_bottom: 0.5
print.print_margin_left: 0.5
print.print_margin_right: 0.5
print.print_margin_top: 0.5
print.print_oddpages: true
print.print_orientation: 0
print.print_page_delay: 50
print.print_paper_data: 0
print.print_paper_height: 11,00
print.print_paper_name:
print.print_paper_size_type: 1
print.print_paper_size_unit: 0
print.print_paper_width: 8,50
print.print_plex_name:
print.print_resolution: 1515870810
print.print_resolution_name:
print.print_reversed: false
print.print_scaling: 1,00
print.print_shrink_to_fit: true
print.print_to_file: false
print.print_unwriteable_margin_bottom: 0
print.print_unwriteable_margin_left: 0
print.print_unwriteable_margin_right: 0
print.print_unwriteable_margin_top: 0
privacy.sanitize.migrateFx3Prefs: true
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1419472934

Important Locked Preferences
----------------------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: false
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.10.8 Beta
Version in use: 4.10.8 Beta

NSS
Expected minimum version: 3.18 Basic ECC Beta
Version in use: 3.18 Basic ECC Beta

NSSSMIME
Expected minimum version: 3.18 Basic ECC Beta
Version in use: 3.18 Basic ECC Beta

NSSSSL
Expected minimum version: 3.18 Basic ECC Beta
Version in use: 3.18 Basic ECC Beta

NSSUTIL
Expected minimum version: 3.18 Beta
Version in use: 3.18 Beta

Experimental Features
---------------------
Flags: needinfo?(silvuss)
This looks like HWA is not enabled for your driver though...

(In reply to Michał Bodziony from comment #2)
> I have run it on Nightly. I have tried it a few times, from (day before
> yesterday?) update it never worked.

Are you saying that before that update, it did work, or that whenever you tried it, it was always broken?

If it's the first (it used to work and now it doesn't), can you try to find out when it broke? Maybe mozregression ( http://mozilla.github.io/mozregression/ ) can help there.
Blocks: e10s
tracking-e10s: --- → ?
Flags: needinfo?(silvuss)
Product: Firefox → Core
Summary: All pages are blank with E10S enabled and hardware acceleration enabled → All pages are blank with E10S enabled
Version: Firefox 38 → Trunk
Before that update these options worked - nothing at all was wrong with displaying pages.

I'll try mozregression, and let you know, when.

And: what could it mean that HWA is not enabled for my driver?
Flags: needinfo?(silvuss)
Flags: needinfo?(silvuss)
(In reply to Michał Bodziony from comment #4)
> And: what could it mean that HWA is not enabled for my driver?

It could mean that your driver is too old. Or, that your hardware is too old for any driver to support HWA.
OK, sorry I'm answering so late.
I have finally managed to install and run mozregression, and these are the results:

The problem is occurring from 2015-01-08, and:
  - the last GOOD revision is 70de2960aa87,
  - the first BAD revision is b30f55f7f94c (application_buildid: 20150107165559).

(I've tried also Safe Mode, and it works even with the newest version, but I have figured out that Safe Mode disables hardware acceleration, so that running in Safe Mode has become senseless.)


(In reply to Wayne Mery (:wsmwk) from comment #5)
> (In reply to Michał Bodziony from comment #4)
> > And: what could it mean that HWA is not enabled for my driver?
> 
> It could mean that your driver is too old. Or, that your hardware is too old
> for any driver to support HWA.

OK, I understand. I've checked I have the newest version of the driver.
But I wonder why the option name is "Use hardware acceleration when available" since it seems not to be available. Maybe this is the root?
Flags: needinfo?(silvuss)
Thanks very much for running mozregression, that's very helpful.

One more thing... can you post the graphics section from the about:support page (Help > troubleshooting information), please? :-)
Component: Untriaged → Graphics
Flags: needinfo?(silvuss)
Keywords: regression
Oh, ugh, I need to read better. Sorry. Milan, can you have a look? (about:support in comment #2, regression window in comment 6)
Flags: needinfo?(silvuss) → needinfo?(milan)
I wonder if this is a regression from bug Bug 1107718. I don't see how it could be though. In order to address this we'll need to get our hands on a machine that exhibits this particular problem.
Whiteboard: [gfx-noted]
There are a few changes in the regression range http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=70de2960aa87&tochange=b30f55f7f94c, I wonder if we could bother Michał for an inbound regression range to narrow it down even further within that day, with something like:

mozregression --inbound --good-rev 70de2960aa87 --bad-rev b30f55f7f94c
Flags: needinfo?(milan)
Flags: needinfo?(silvuss)
Assignee: nobody → davidp99
I've just tried narrow it down with the above command, but the result is that there are no inbound revisions ("Oh noes, no (more) inbound revisions :(").
Flags: needinfo?(silvuss)
Jouan, can you help Michał here?
Flags: needinfo?(jbecerra)
(In reply to Michał Bodziony from comment #11)
> I've just tried narrow it down with the above command, but the result is
> that there are no inbound revisions ("Oh noes, no (more) inbound revisions
> :(").

I think it always says that at the end (which seems unfortunate to me). If you didn't have any problems reducing the range up until that point, the range it gives should be correct, even if there are broken builds in between.
Oh I see, there's backouts for build bustage at the end of that range, so there probably are no successful builds in between. In that case you'll need local/try builds with bug 1118328 backed out for various points in that range.
I wasn't able to reproduce this on hardware on Win8.1 using mozregression.

Using the try builds above I started seeing pages that just show the spinner when using changeset d2ec9f25f00c on a Windows 7 VM. It would often crash: d579d935-1b28-4ead-8e39-f28162150202

I haven't been able to reproduce the problem as described in comment #0. I think may be hardware dependent.
Flags: needinfo?(jbecerra)
Sorry I haven't written for so long time, I have now my examination session. I'd thought I could've been able to try these builds earlier, but now I know that I can do it next Sunday earliest.
Ok, I have finally managed to install and check the above builds given by Emanuel. So, I'm writing the results.

For each build, I have installed it in a new, individual folder, and run using a new, individual profile. Every time I have tried to load https://www.google.pl/?gws_rd=ssl. I've checked two cases: loading with the default state of E10S (=enabled) and hardware acceleration (=disabled), and loading with both enabled.

Loading with the default state was OK for every build.

Loading with both options enabled was:
Builds 4a1879ef4d01, 26b9c7636079, 980e8272acfc, 476737441eed, c24a919c098c loaded the site with no problems.
Build 3b530138c8c0 showed the Nightly window for a while, then it crashed and the 'Mozilla Crash Reporter' window appered. After clicking 'Restart Firefox', it crashes again.
Build aad3d78c0464 didn't show the Nightly window, it immediately crashed showing the 'Mozilla Crash Reporter' window. After clicking 'Restart Firefox' it crashed again.
Build d2ec9f25f00c immediately crashed showing the 'Mozilla Crash Reporter' window. After clicking 'Restart Firefox' it crashed again.

My antivirus is COMODO Internet Security; I thought that for these three builds I should try to run them in sandbox. But the results were different only for build 3b530138c8c0: Nightly ran, but when I tried to load a site, it crashes.


I hope my results would be useful. :)
Flags: needinfo?(silvuss)
And sorry for answering so late. Just yesterday I finished my examination session.
Thank you for testing! Since d2ec9f25f00c was the first build to crash, bug 1107718 must be responsible for the crashes.

That being said, crashing isn't the same problem as the one you originally reported, so it's also possible that something went wrong with the regression range. When you were using mozregression, did you accept builds that crashed as 'bad' or did you skip them?

You should also consider testing to see if this is fixed in the latest Nightly. If it is, you can also use mozregression to figure out when the problem was *fixed*, which might be equally useful.

Finally, since HWA is disabled for you by default, how are you enabling it? What does the Graphics section of about:support say when you're using a new profile? It may be that HWA is known to not work correctly on your hardware (although it's odd that *e10s* would cause a problem).
Ups, sorry, my mistake, E10S is DISABLED by default and HWA is ENABLED by default.

With mozregression, I skipped the builds that crashed.

As I've checked a moment ago, this is not fixed in the latest Nightly.

I have pasted my about:support above, but I don't know whether it was on a new profile. So, this is my about:support for a new profile (by the way, I noticed that on the tab I'd tried to load a site, about:support doesn't work, only on a new tab or tab with, for example, options):


Application Basics
------------------

Name: Firefox
Version: 38.0a1
Build ID: 20150216030222
Update Channel: nightly
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0
Multiprocess Windows: 1/1 (default: true)

Crash Reports for the Last 3 Days
---------------------------------

All Crash Reports (including 2 pending crashes in the given time range)

Extensions
----------

Name: Bytemobile Optimization Client
Version: 4.2.2
Enabled: false
ID: ff-bmboc@bytemobile.com

Graphics
--------

Adapter Description: Intel(R) Graphics Media Accelerator 3600 Series
Adapter Drivers: igdumd32
Adapter RAM: Unknown
Device ID: 0x0be1
Direct2D Enabled: Blocked for your graphics driver version.
DirectWrite Enabled: false (6.2.9200.16571)
Driver Date: 2-27-2012
Driver Version: 8.14.8.1075
GPU #2 Active: false
GPU Accelerated Windows: 0/1 Basic (OMTC) Blocked for your graphics driver version.
Subsys ID: 061f1025
Vendor ID: 0x8086
WebGL Renderer: Blocked for your graphics driver version.
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Important Modified Preferences
------------------------------

browser.cache.disk.capacity: 286720
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 3
browser.download.importedFromSqlite: true
browser.places.smartBookmarksVersion: 7
browser.startup.homepage_override.buildID: 20150216030222
browser.startup.homepage_override.mstone: 38.0a1
dom.mozApps.used: true
extensions.lastAppVersion: 38.0a1
media.gmp-gmpopenh264.lastUpdate: 1424170804
media.gmp-gmpopenh264.version: 1.3
media.gmp-manager.lastCheck: 1424170804
network.cookie.prefsMigrated: true
places.history.expiration.transient_current_max_pages: 30147
plugin.disable_full_page_plugin_for_types: application/pdf
privacy.sanitize.migrateFx3Prefs: true

Important Locked Preferences
----------------------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: false
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.10.8
Version in use: 4.10.8

NSS
Expected minimum version: 3.17.4 Basic ECC
Version in use: 3.17.4 Basic ECC

NSSSMIME
Expected minimum version: 3.17.4 Basic ECC
Version in use: 3.17.4 Basic ECC

NSSSSL
Expected minimum version: 3.17.4 Basic ECC
Version in use: 3.17.4 Basic ECC

NSSUTIL
Expected minimum version: 3.17.4
Version in use: 3.17.4

Experimental Features
---------------------
Hm, Emanuel, as I can understand, do you want me to check which builds crashed when I were using mozregression?
If you skipped crashing builds while using mozregression, the range should be correct. It's strange that the try builds I linked would crash when you're not seeing crashes on the last revision of your range (b30f55f7f94c) though.

I would ask you to check if you see crashes with this build, but unfortunately the archived mozilla-inbound builds on [1] no longer go back far enough to include the builds from your regression range.

Do you see the problem you described (all pages are blank with e10s enabled) with any of the last 3 builds I linked, or do they all crash instantly instead? Also, could you post signatures from a few of those crashes here? (check about:crashes)

[1] https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/
Flags: needinfo?(davidp99)
So... I don't know exactly, what I have to do with [1] ?

As I remember, all three builds crashed immediately after trying to run them with E10S and HWA both enabled; the only doubt I've got would be with, as I remember, build d2ec9f25f00c. I would check them again, but I've deleted files from my computer, and the archives that you show links above are now unavailable.

Unfortunately, I've uninstalled the builds and deleted profiles, so I cannot check about:crashes.
Thanks for sticking with this, Michal.

There may be a later driver that you can try for your graphics card.  That could take care of your problem.  According to your about:config stats, your driver version is 8.14.8.1075 but the latest at intel.com is 8.14.8.1096.  I'm looking at: https://downloadcenter.intel.com/SearchResult.aspx?ProdId=3468&lang=eng

If the drivers aren't helpful, can you post the Graphics section from your about:config... but this time having launched with HWA turned on (I think it was off last time)?  This will give us a little more info on your hardware.
Flags: needinfo?(davidp99) → needinfo?(silvuss)
OK, I've just installed the new driver - thanks, David, for remind me that it was the issue I hadn't handled by now.

So, the Graphics section is (and I launched Nightly with HWA and E10S enabled):

Adapter Description: Intel(R) Graphics Media Accelerator 3600 Series
Adapter Drivers: igdumd32
Adapter RAM: Unknown
Device ID: 0x0be1
Direct2D Enabled: Blocked for your graphics driver version.
DirectWrite Enabled: false (6.2.9200.16571)
Driver Date: 10-23-2013
Driver Version: 8.14.8.1096
GPU #2 Active: false
GPU Accelerated Windows: 0/1 Basic (OMTC) Blocked for your graphics driver version.
Subsys ID: 061f1025
Vendor ID: 0x8086
WebGL Renderer: Blocked for your graphics driver version.
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0


Hm... I haven't look at that section before, but now... could this be the cause of my problem: "GPU Accelerated Windows: 0/1 Basic (OMTC) Blocked for your graphics driver version." ?...
Flags: needinfo?(silvuss)
Thanks Michal.  When you are turning on HWA in about:preferences, you are actually toggling the about:config setting 'layers.acceleration.disabled'.  In particular, you are not guaranteed to get HWA by doing this... and you are not getting HWA because Firefox is blocking it based on your hardware configuration.  This is the first mystery -- its not clear to me why your card is blocked.  The "Basic GPU Accelerated Windows" are using Firefox's software-based graphics pipeline.

So things work for you with the HWA setting off but, with the HWA setting on but blocked/ignored... somehow this creates failure.  This is also mysterious.

Does your machine have another graphics card (and if so, what)?  Rarely, the reported hardware configuration is wrong and dual graphics cards get incorrectly reported.

Also, are you using a GPU-vendor control panel like an NVidia or Intel program that allows you to configure your GPU to specific programs?  If you have used something like that to set the GPU for Firefox, it might need to be fixed.  If this doesn't make any sense to you then you can ignore it.

Finally, there's a little confusion here over the nature of the bug.  The initial bug was that all pages were blank but your mozregression window only mentioned builds either working (presumably with not all blank pages) or crashing.  You also report that the latest Nightly build doesn't work -- I take it to mean that it crashes as well.  If thats true, can you reproduce the crash with Nightly and report it from about:crashes?  Also, since things are constantly crashing, I assume you haven't seen the initial 'blank pages' bug in a while?  The crash may be a separate issue that we need to fix before we can even deal with the blank pages.
Flags: needinfo?(silvuss)
Thanks, David, you clarified the things for me.

(In reply to David Parks [:handyman] from comment #27)
> Finally, there's a little confusion here over the nature of the bug.  The
> initial bug was that all pages were blank but your mozregression window only
> mentioned builds either working (presumably with not all blank pages) or
> crashing.  You also report that the latest Nightly build doesn't work -- I
> take it to mean that it crashes as well.  If thats true, can you reproduce
> the crash with Nightly and report it from about:crashes?  Also, since things
> are constantly crashing, I assume you haven't seen the initial 'blank pages'
> bug in a while?  The crash may be a separate issue that we need to fix
> before we can even deal with the blank pages.

I'll start maybe from the end of your post, as it's the main thing. Using mozregression, some builds were working (that is, some sites I have tested were displayed with no problems, so I assumed that all sites would work, so marked these builds as working), some builds were crashing, but some of them were showing the initial bug.
The latest Nightly build didn't crash - it was showing the initial bug (all pages are blank).

> Does your machine have another graphics card (and if so, what)?  Rarely, the
> reported hardware configuration is wrong and dual graphics cards get
> incorrectly reported.

No other graphics card. My machine is Acer Aspire One (http://www.acer.com.ph/ac/en/PH/content/model/NU.SGDSP.006). Well, this is embarrassing for me I hadn't mentioned it before...

> Also, are you using a GPU-vendor control panel like an NVidia or Intel
> program that allows you to configure your GPU to specific programs?  If you
> have used something like that to set the GPU for Firefox, it might need to
> be fixed.  If this doesn't make any sense to you then you can ignore it.

No, I don't use it (and never used, maybe just to see what it is, some time ago, as I understand you mean e.g. Intel® Graphics Control Panel).

One more thing... I installed new Nightly before about two hours, and I thought I should try whether it works or not. When I launched it, Google and Firefox start page loaded with no problems. I checked the options and... both E10S and HWA was enabled. Problem solved? But... I thoght I should try it with any combination of the options, just to make sure (some sort of habit ;) ). So, I disabled HWA and restarted. No problems with Google. So, I disabled E10S and restarted. No problems with Google. So, I enabled E10S and disabled HWA and restarted. No problems with Google. So, I enabled both and restarted. The initial bug still exists.
Flags: needinfo?(silvuss)
Sorry, I wrote 'The latest Nightly build didn't crash - it was showing the initial bug (all pages are blank)', but it should be 'is showing', since the latest Nightly shows the bug.
(In reply to Michał Bodziony from comment #28)
>
> One more thing... I installed new Nightly before about two hours, and I
> thought I should try whether it works or not. When I launched it, Google and
> Firefox start page loaded with no problems. I checked the options and...
> both E10S and HWA was enabled. Problem solved? But... I thoght I should try
> it with any combination of the options, just to make sure (some sort of
> habit ;) ). So, I disabled HWA and restarted. No problems with Google. So, I
> disabled E10S and restarted. No problems with Google. So, I enabled E10S and
> disabled HWA and restarted. No problems with Google. So, I enabled both and
> restarted. The initial bug still exists.

Thanks for the detail.  If you can get back to the state you describe here (where things were working and both e10s and HWA were set), try posting the Graphics section of about:support.  In particular, I'm wondering if HWA was actually active there since its being blocked for you otherwise (...and I'm not sure why).
An interesting thing (with the latest Nightly): with a new profile, either I refresh the tab or switch to the other tab, or load another page in a new tab, all the pages are loading correctly (in all tabs). But when I start typing in the address bar (doesn't matter on which tab, and doesn't matter if I press enter), all the pages in all the tabs go blank (that's not occurring when I just click the address bar, i.e. set the cursor in it).
After switching to the other application, and then switching again to Nightly, the pages go blank.
After restarting Nightly with the same profile, all pages are blank, but... with one profile, I tried this, and after restarting Google loaded correctly (I typed it in the address bar), but the next page (I typed again) not.
And after creating new profile, the pages are loading correctly again.

I feel like there is a relationship between switching from the tab to the other or to another application and going blank.

If I explained it not clearly, tell me, I'll try clarify.

So, David, my about:support, graphics section, is (I paste it, not typed, and I checked, all the pages are loading correctly):

Graphics
--------

Adapter Description: Intel(R) Graphics Media Accelerator 3600 Series
Adapter Drivers: igdumd32
Adapter RAM: Unknown
Device ID: 0x0be1
Direct2D Enabled: Blocked for your graphics driver version.
DirectWrite Enabled: false (6.2.9200.16571)
Driver Date: 10-23-2013
Driver Version: 8.14.8.1096
GPU #2 Active: false
GPU Accelerated Windows: 0/1 Basic (OMTC) Blocked for your graphics driver version.
Subsys ID: 061f1025
Vendor ID: 0x8086
WebGL Renderer: Blocked for your graphics driver version.
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
Flags: needinfo?(davidp99)
I haven't managed to reproduce this issue on the latest Aurora build(46.0a2). With e10s and HWA enabled, any page I navigated to was correctly displayed. None on them were black, nor the browser crashed.

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160204004009

Considering this, I will mark this issue as RESOLVED WORKSFORME. If you still encounter this problem, please feel free to reopen this bug, or file a new one.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(davidp99)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.