Firefox 144.0.2 fixes stability issues and OneDrive rendering bug on Windows and macOS

Mozilla has quietly shipped Firefox 144.0.2, a targeted point release that patches a clutch of stability regressions first seen after the 144 series, fixes a OneDrive rendering problem, and smooths a handful of platform-specific integration issues that have been inconveniencing Windows and macOS users. The update is small in scope but significant in impact: it corrects deterministic startup and plugin-related crashes, resolves a OneDrive “For You” photo collection blank-screen bug, and cleans up several UI and interoperability edge cases introduced with the 144 release.

Background​

Firefox 144 arrived in mid‑October as a typical feature-and-fix major update; its changelog included tab-group refinements, profile management improvements, visual-search options and a set of security hardenings. Those changes were broadly welcomed, but, as often happens with major releases, follow-on stability work was required to resolve platform-specific regressions revealed by real‑world usage and telemetry. Mozilla’s engineering teams moved quickly through the 144.x branch, culminating in the 144.0.2 point release published on Mozilla’s public release channels and mirrored on the official FTP repository. The timing and distribution model are worth noting: Mozilla uses staged rollouts for stable releases, and the 144.x series followed a fast cadence of follow-up fixes once crash telemetry and user reports started trending. That meant targeted micro‑patches rather than a full redesign — the kind of surgical maintenance that restores day‑to‑day reliability for the majority of users.

---

What exactly 144.0.2 fixes​

144.0.2 is composed of a handful of practical fixes rather than large feature additions. The key items addressed in the release notes and associated bug reports include:

• Windows startup and crash fixes: several crash scenarios that produced ERROR_INVALID_HANDLE or ERROR_INVALID_PARAMETER when Windows Exploit Protection or certain antivirus/endpoint hooks were present have been healed. These were observed both in Store‑distributed installs and traditional downloads under specific system mitigation settings.
• OneDrive “For You” curated photo collections: a rendering bug where curated photo collections on the For You page of Microsoft OneDrive displayed a gray screen or failed to load in Firefox has been corrected. This resolves a usability break for users who access OneDrive content directly from emails or the web interface in Firefox.
• Third‑party integration/antivirus interactions: fixes were included for startup crashes affecting Windows users running Avast and other security tooling that inject DLLs or alter low-level I/O behavior. Mozilla’s engineering notes and follow-up bug entries identify injected DLLs and ValidateHandle‑style checks as causal factors in several crash reports.
• Locale and UI keyboard inconsistencies: corrected an issue where the list of available locales in about:settings showed more locales than were actually supported or installed, and where keyboard access to the Unified Search drop‑down menu could behave inconsistently. These are quality‑of‑life fixes for accessibility and international users.
• macOS regressions: a set of macOS‑specific fixes addressed emoji picker shortcut regressions and drag‑and‑drop image behavior that caused failures when images were dragged from Firefox into macOS Preview or other apps, along with performance/video playback improvements for heavily utilized macOS 14.6 systems.

These fixes were small but high‑leverage: they resolve deterministic failures and restore expected behaviour for common cross‑app interactions. The presence of FTP build artifacts dated with the 144.0.2 tag confirms the formal release and availability across locales and packages.

---

Technical root causes: what went wrong and why​

Two technical themes recur across the crash reports and bug entries:

• Platform mitigations exposing brittle handle usage
  The crashes tied to ERROR_INVALID_HANDLE / ERROR_INVALID_PARAMETER were traced to code paths that interact with Windows APIs expecting valid handles (CloseHandle, CancelIoEx, WriteFile, etc.. When Windows Exploit Protection or endpoint tools are configured to validate handle usage more strictly, previously tolerated coding patterns could fail fast. Mozilla’s bug tracker and developer notes show these failures manifest when a parent or helper process receives unexpected or invalid handles from child processes or injected code, leading to immediate process termination. This class of bug is deterministic and reproducible on systems with the particular mitigation settings turned on.
• Third‑party runtime injection and DLLs
  Many antivirus, DLP and other endpoint products use DLL injection or loader hooks to observe or modify browser behaviour. Those injected modules sometimes interact poorly with new internal browser behaviors introduced in a major release, producing crashes or unexpected errors. Mozilla has been actively encouraging vendors to move to supported integration patterns (for example, using the Content Analysis SDK where available) to reduce the fragility caused by undocumented hooks. Until the ecosystem converges, short‑term patches in the browser remain necessary to tolerate the diversity of endpoint agents in the field.

The result: 144.0.2 is not a feature update so much as an interoperability patching pass — it hardens Firefox's startup and I/O code paths so they are resilient when the underlying OS or third‑party agents apply stricter validation.

---

Security context and related advisories​

Firefox 144 as a major release also bundled several security fixes (several high‑severity CVEs were closed in the 144 release cycle). Some of the vulnerabilities patched in the 144 baseline were significant memory‑safety and IPC issues that could allow process privilege escalation or cross‑process memory leaks if exploited. The 144.0.2 point release primarily addresses stability and interoperability; it is not primarily a security advisory, but it arrives in the context of a broader security update cycle for Firefox. When a release includes both security hardening and reliability work, administrators should treat it as high priority for update—even when individual point patches look narrow—because the underlying risk surface (IPC, sandboxing, and third‑party integrations) is shared between stability and security failure modes.

---

Who was affected, and how to tell​

• Windows users with Exploit Protection enabled — including users with Store installs: Many of the deterministic startup crashes were reproducible on systems where Exploit Protection rules validate handle usage more aggressively. Because Microsoft Store distributed apps are frequently launched under additional platform-level mitigations, Store‑installed Firefox builds were disproportionately represented in early crash reports. Traditional installers could also be affected when Exploit Protection was set system‑wide.
• Machines with AV/DLP injection — users running certain antivirus or endpoint agents (Avast and similar products were specifically called out in some bug reports) saw startup or runtime crashes tied to DLL injection behaviors. If you experienced crashes and your crash module list contains vendor DLL names in the abort stack, that is a strong signal this class of incompatibility may be involved.
• OneDrive “For You” users — people who clicked OneDrive “memories” or “for you” links and saw a gray screen were impacted by the OneDrive rendering bug. The fix landed in 144.0.2 and is intended to restore curated photo collection rendering in the For You page. Mozilla support threads and the bug tracker explicitly tie that fix to the 144.0.2 patch.

How to tell if you were affected:

• Firefox crash reports saved in about:crashes that include ERROR_INVALID_HANDLE / ERROR_INVALID_PARAMETER or mention CancelIoEx/CriticalHandle failures point to the Exploit Protection/handle validation issue.
• If OneDrive pages showed a persistent gray box where collections should display, the 144.0.2 update should resolve that. Verify by updating and refreshing OneDrive pages.

---

Practical guidance: what users and admins should do now​

For most end users:

• Update to Firefox 144.0.2 via the browser’s built‑in updater or download the official installer if you prefer manual installs. The fixed builds are available on Mozilla’s servers and via the normal release channels.
• If crashes persist after updating, launch Firefox in Safe Mode (which disables extensions and certain accelerations) to determine whether an extension or runtime hook is causal. Use about:crashes to inspect report details.
• For OneDrive rendering issues, update and then clear the page cache; if the problem persists, try a profile without extensions to eliminate an extension-level interference.

For IT administrators:

• Prioritize deployment of the 144.0.2 build to endpoints particularly exposed to Exploit Protection policies or running third‑party security agents. This update is a reliability patch that will reduce help‑desk noise from deterministic startup failures.
• Inventory endpoint agents and update AV/DLP vendors to their latest versions. Encourage vendors to adopt supported integration APIs rather than DLL injection where feasible. Mozilla has been publishing guidance on supported integration patterns for enterprise content analysis and similar scenarios.
• Use Firefox Enterprise policies to stage the update and to pin or delay channels if needed for compatibility testing. Where stability is critical, run a pilot cohort for 48–72 hours and gather crash telemetry prior to fleetwide rollout.

---

Critical analysis: strengths, trade‑offs, and lingering risks​

Strengths

• Rapid, surgical remediation: 144.0.2 demonstrates a disciplined, focused engineering response to concrete regressions — the type of small, high‑impact patch enterprises want during a major release cycle. Rapid fixes reduce user disruption and avoid noisy downgrade cycles.
• Cross‑platform attention: the release addresses problems on both Windows and macOS, reflecting a balanced approach to platform compatibility rather than a single‑platform focus. That is important in heterogenous fleets where macOS quirks can be as disruptive as Windows crashes.
• Proactive bug tracking and communication: Mozilla’s public bug tracker entries and support forum notes make it straightforward to verify whether a specific bug has been addressed in a given point release. That transparency is helpful for IT triage.

Trade‑offs and residual risks

• Ecosystem fragility remains: the root cause of many crashes is not strictly a Firefox bug alone but the interplay between browser internals, OS mitigations and third‑party agents. Until the broader ecosystem adopts more robust (and documented) integration points, these coordination problems will recur. Relying on browser-side hardening alone can add maintenance burden.
• Delayed vendor coordination: endpoint vendors and antivirus authors do not always publish compatibility timelines in lock‑step with browser vendors. Organizations may face short windows where either the browser or endpoint agent must be updated first, complicating change-control workflows.
• Visibility limitations: crash metadata is helpful but not always definitive — a referenced DLL in a crash report is a signal, not a proof of sole causation. Reproducing the crash with the agent disabled is still the most reliable method to confirm root cause. Administrators must retain troubleshooting capability and not assume a single quick fix is universal.

---

A short checklist for troubleshooting persistent issues​

• Update Firefox to 144.0.2 and reboot the machine.
• If the crash persists, start Firefox in Safe Mode: hold Shift while launching or use the Safe Mode option. If it runs, investigate extensions and acceleration settings.
• Inspect about:crashes and attach crash IDs when opening bug reports; note the module list — injected DLLs are often the differentiator.
• Temporarily disable or update AV/DLP agents in coordination with your vendor. If disabling removes the crash, escalate to the endpoint vendor for a compat fix.
• For OneDrive rendering problems, clear Firefox’s cache and verify with a clean profile; the 144.0.2 fix should address the For You page issue.

---

What this release tells us about modern browser maintenance​

The 144.0.2 cycle is an instructive micro‑case in modern browser maintenance: major functional evolution (tabs, profiles, AI/visual search options) moves in parallel with intense stability monitoring, and vendors must be nimble enough to ship surgical fixes when real‑world telemetry surfaces platform interactions the QA lab didn’t exercise. It underscores three operational realities for IT:

• You cannot treat browsers as immutable appliances; aggressive change cadence requires staged deployments and strong telemetry collection.
• Browser reliability is a joint responsibility across OS vendors, endpoint toolmakers and browser teams; coordination and documented integration APIs reduce breakage blasts.
• Small, focused patches can materially improve user experience and reduce support costs even when they don’t add features.

Taken together, that explains why organizations that manage fleets at scale adopt a pattern of pilot → staged rollout → fleetwide deployment, and why they rely on ESR or pinned channels for mission‑critical endpoints that cannot tolerate frequent changes.

---

Final verdict and recommendations​

Firefox 144.0.2 is a pragmatic and necessary follow‑up to the 144 series. It fixes deterministic, high‑impact crashes that affected Windows users in specific configurations, resolves an important OneDrive rendering bug, and cleans up several cross‑platform user‑experience regressions. For everyday users, the update is low risk and high reward: install it. For administrators, the release should be elevated in deployment plans for affected cohorts (those with Store installs, aggressive Exploit Protection settings, or heavy endpoint agent footprints).
Recommended immediate actions:

• Desktop users: update to 144.0.2 and restart. Verify OneDrive pages if you had a rendering problem.
• IT teams: run a targeted pilot on endpoints with known AV/DLP agents, coordinate with security vendors for compatible agents, and use Enterprise policies to stage the rollout.

This release is not a headline feature drop; it is a reminder that maintenance matters. In an environment of rapid feature delivery, the quiet work of fixing stability regressions keeps the browser useful, predictable and safe for the billions of interactions it authorizes every day.

---

---

Source: Neowin Firefox 144.0.2 is out with fixes for crashes on Windows, OneDrive issues, and more