{"id":29458,"date":"2023-04-26T02:50:05","date_gmt":"2023-04-26T00:50:05","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=29458"},"modified":"2024-10-05T19:04:20","modified_gmt":"2024-10-05T17:04:20","slug":"firefox-112-0-2-fix-for-memory-leak","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2023\/04\/26\/firefox-112-0-2-fix-for-memory-leak\/","title":{"rendered":"Firefox 112.0.2: Fix for Memory Leak"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"margin: 0px 10px 0px 0px;\" title=\"Firefox\" src=\"https:\/\/i.imgur.com\/Dhputf4.jpg\" alt=\"Mozilla\" width=\"65\" height=\"63\" align=\"left\" border=\"0\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2023\/04\/25\/firefox-112-0-2-fix-fr-hohen-speicherverbrauch\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]The Mozilla developers have probably corrected the bug in Firefox 112.0.1, which led to high memory consumption with version 112.0.2. As of April 25, 2023, the maintenance update to version 112.0.2 has been released, which is supposed to fix the bug.<br \/>\n<!--more--><\/p>\n<p>Techdows had reported in this post a few days ago that Firefox 112.0 was using an extremely large amount of memory and could probably have a memory leak. I had seen that in <a href=\"https:\/\/twitter.com\/techdows\/status\/1650042693391896576\" target=\"_blank\" rel=\"noopener\">this tweet<\/a>, but had not addressed it here on the blog. Martin Brinkmann had then reported in <a href=\"https:\/\/twitter.com\/ghacks\/status\/1650450160005120000\" target=\"_blank\" rel=\"noopener\">that tweet<\/a> and in <a href=\"https:\/\/web.archive.org\/web\/20230429132228\/https:\/\/www.ghacks.net\/2023\/04\/24\/mozilla-confirms-memory-leak-in-firefox\/\" target=\"_blank\" rel=\"noopener\">this article<\/a> that the Mozilla developers had confirmed the memory leak.<\/p>\n<h2>Firefox 112.0.2<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg07.met.vgwort.de\/na\/13c3dbfbbdab43189c2fc0f50798c8eb\" alt=\"\" width=\"1\" height=\"1\" \/>Now the developers have released Firefox 112.0.2, which, according to the <a href=\"https:\/\/www.mozilla.org\/en-US\/firefox\/112.0.2\/releasenotes\/\" target=\"_blank\" rel=\"noopener\">release notes<\/a>, brings the fixes listed below on April 25, 2023.<\/p>\n<ul>\n<li>Fixes a high memory usage issue with animated images in minimized (or completely covered) windows, especially when using animated themes (bug 1828587).<\/li>\n<li>Fixes an issue where Linux users with bitmap fonts installed may have had entire sections of text invisible to them on some sites (bug 1827950).<\/li>\n<li>Fixes an issue where web notifications with images were not displaying for Windows 8 users (bug 1822817).<\/li>\n<\/ul>\n<p>So the memory leak on Windows has been fixed. Firefox should update itself automatically, but can be downloaded from <a href=\"https:\/\/www.mozilla.org\/de\/firefox\/all\/#product-desktop-release\" target=\"_blank\" rel=\"noopener\">this website<\/a> for various platforms (the variant is to be selected via the list boxes displayed).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]The Mozilla developers have probably corrected the bug in Firefox 112.0.1, which led to high memory consumption with version 112.0.2. As of April 25, 2023, the maintenance update to version 112.0.2 has been released, which is supposed to fix the &hellip; <a href=\"https:\/\/borncity.com\/win\/2023\/04\/26\/firefox-112-0-2-fix-for-memory-leak\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,1547,22],"tags":[530],"class_list":["post-29458","post","type-post","status-publish","format-standard","hentry","category-browser","category-software","category-update","tag-firefox"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/29458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=29458"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/29458\/revisions"}],"predecessor-version":[{"id":35735,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/29458\/revisions\/35735"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=29458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=29458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=29458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}