Mozilla Firefox 59.0.2 is out

Mozilla just released another bugfix release which fixes several issues reported within the official bugtracker.



You get the update via the internal update mechanism or you can download it manually via the secured ftp server over here.


The full changelog is as always available over here.

  • Invalid page rendering with hardware acceleration enabled
  • Windows 7 users with touch screens or certain 3rd party desktop applications which interact with Firefox through accessibility services may experience random browser crashes. Known 3rd party applicatioins with issues: StickyPassword, Windows 7 touch screen.
  • Browser keyboard shortcuts (eg copy Ctrl+C) don’t work on sites that use those keys with resistFingerprinting enabled
  • High CPU / memory churn caused by third-party software on some computers
  • Users who have configured an “automatic proxy configuration URL” and want to reload their proxy settings from the URL will find the Reload button disabled in the Connection Settings dialog when they select Preferences/Options > Network Proxy > Settings…
  • URL Fragment Identifiers Break Service Worker Responses
  • User’s trying to cancel a print around the time it completes will continue to get intermittent crashes
  • Broken getUserMedia (audio) on DragonFly, FreeBSD, NetBSD, OpenBSD. Video chat apps either wouldn’t work or be always muted
  • Security fix: A use-after-free vulnerability can occur in the compositor during certain graphics operations when a raw pointer is used instead of a reference counted one. This results in a potentially exploitable crash.

About:Config changes

There no changes in this build, since this is only a bugfix release.

Closing Words

This is another bugfix release following the security update 59.0.1, why Mozilla is releasing one bugfix release after another so fast is beyond me. The mentioned security update in the changelog needs several circumstances in order to crash the Browser, it’s not really ‘security’ related more a problem to harden the raw pointers by itself and a possible coding flaw.

However, I like to see it positive that Mozilla reacted quickly even if some of the fixed things have been already reported months ago over the bug-hunting program but that seems a global problem since not only Mozilla is affected by this and this means we need to pay more attention to reported problems.