Bug 19276: Disable Xrender due to possible performance regressions.Bug 19348: Adapt to more than one build target on Windows (fixes updates).Bug 19400: Back out GCC bug workaround to avoid asmjs crash.Bug 19411: Don't show update icon if a partial update failed.Bug 19401: Fix broken PDF download button.See bug 19400 for more details in this regard. 2) As files cached by those websites in the Tor Browser profile are causing the crashes, deleting them helps as well. There are at least two workarounds for this: 1) Using a clean new Tor Browser 6.0.2 (including a new profile) solves the problem. We suspect this happens because those users are not using Tor Browser in its default configuration but have left the Private Browsing Mode. Update (June 23, 12:38 UTC): We have still some users that report crashes on Facebook and mega.nz. The internal updater should still work, though, doing a complete update. An other effect is that the incremental update will not be working for users who installed the previous version using the. A side effect of this signature is that it makes it harder to compare the bundles we ship with the bundles produced using reproducible builds, therefore we plan to post instructions for removing the OS X code signing parts on our website soon. Note: In version 6.0 we started code signing the OS X bundle for Gatekeeper support. on Faceboook or mega.nz and we fixed the broken PDF download button in the PDF reader. In particular, we resolved a possible crash bug visible e.g. Tor Browser 6.0.2 is a fixup release to address the most pressing issues we found after switching to Firefox 45.2.0esr. Tor Browser 6.0.2 is now available from the Tor Browser Project page and also from our distribution directory.
0 kommentar(er)
