Merge latest firefox 140 commits 13/03/2026#5
Merged
Conversation
Differential Revision: https://phabricator.services.mozilla.com/D285858
…a=pascalc Also update the readme to mention git instead of hg. Original Revision: https://phabricator.services.mozilla.com/D278890 Differential Revision: https://phabricator.services.mozilla.com/D286429
Generated using mach vendor parser/expat/moz.yaml --patch-mode=none Original Revision: https://phabricator.services.mozilla.com/D278891 Differential Revision: https://phabricator.services.mozilla.com/D286430
* Mostly, this unbitrots the patches and updates line numbers.
* Define MOZ_XML_GetMismatchedTag and MOZ_XML_ProcessingEntityValue in
moz_xmlparse.c instead of these patches, to reduce future bitrot. This means
that 06_report_processing_entity.patch can be removed entirely.
* For 06_always_store_rawnames.patch, in the section from line 33 to 71 nothing
is really changing. The old diff was just really awful for some reason. For
the final chunk from line 72 to 86, that chunk of code with a call to
storeRawNames in internalEntityProcessor, so it could be deleted.
* 11_nested_entities.patch handles some kind of issue with nested entities.
This seems to correspond to code in internalEntityProcessor where there
is now an assertion:
assert(parser->m_openInternalEntities == openEntity);
So I guess it is no longer needed. Peter removed it from his patch stack.
* Renumber the patches to account for the two removed ones.
* In 11_no_debug_report.patch, a new struct MALLOC_TRACKER has been added.
I had to remove new debugLevel here, as well as peakBytesAllocated, which
as it says is only used when debugLevel is set. expat_heap_stat is also
only used by that code, so it gets removed, too.
* 12_unused.patch removes a bunch of unused code. The stuff around line 56
had to change because a new function, parserBusy, that is used was added
into the middle of a bunch of unused functions.
Original Revision: https://phabricator.services.mozilla.com/D278892
Differential Revision: https://phabricator.services.mozilla.com/D286431
This was auto generated with ./mach vendor parser/expat/moz.yaml --patch-mode=only Original Revision: https://phabricator.services.mozilla.com/D278893 Differential Revision: https://phabricator.services.mozilla.com/D286432
Original Revision: https://phabricator.services.mozilla.com/D281333 Differential Revision: https://phabricator.services.mozilla.com/D286433
…ascalc Original Revision: https://phabricator.services.mozilla.com/D283719 Differential Revision: https://phabricator.services.mozilla.com/D286434
Original Revision: https://phabricator.services.mozilla.com/D283720 Differential Revision: https://phabricator.services.mozilla.com/D286435
Original Revision: https://phabricator.services.mozilla.com/D283721 Differential Revision: https://phabricator.services.mozilla.com/D286436
…ixes ct-logs - a=pascalc DONTBUILD Differential Revision: https://phabricator.services.mozilla.com/D286664
…ascalc DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D284097 Differential Revision: https://phabricator.services.mozilla.com/D285705
Original Revision: https://phabricator.services.mozilla.com/D283147 Differential Revision: https://phabricator.services.mozilla.com/D285742
Original Revision: https://phabricator.services.mozilla.com/D283757 Differential Revision: https://phabricator.services.mozilla.com/D285790
…onstruction. a=pascalc Instead of sending a separate message, immediately do the initialization after the actor is created and registered, via a new override of RecvPContentPermissionRequestConstructor. I didn't move the initialization inside AllocPContentPermissionRequestParent because the Init() method runs JS so it seems like a bad idea to do when the actor isn't fully set up. aRequests is now set inside the Init() method instead of the constructor, which allows us to avoid a copy of this array at the low cost of making the diff gross. Original Revision: https://phabricator.services.mozilla.com/D284774 Differential Revision: https://phabricator.services.mozilla.com/D286018
…lag() is only called for ServiceWorker. a=pascalc DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D284639 Differential Revision: https://phabricator.services.mozilla.com/D285929
Differential Revision: https://phabricator.services.mozilla.com/D285854
…assID` a=pascalc DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D285201 Differential Revision: https://phabricator.services.mozilla.com/D286407
…d `WidgetWheelEvent` a=pascalc DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D285911 Differential Revision: https://phabricator.services.mozilla.com/D286445
Original Revision: https://phabricator.services.mozilla.com/D283433 Differential Revision: https://phabricator.services.mozilla.com/D286497
…yData() a=pascalc DONTBUILD and assert that plane sizes match subsampling. Original Revision: https://phabricator.services.mozilla.com/D285683 Differential Revision: https://phabricator.services.mozilla.com/D286514
…=pascalc DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D285684 Differential Revision: https://phabricator.services.mozilla.com/D286515
…DONTBUILD The parent process should handle only the shortcut key and access key when it receives a reply key event. Thus, the editor commands are not required, but the copy cost may not be cheap. Therefore, we should stop copying them and the parent process should check whether the reply event has unexpected edit commands or not. And also this makes `nsGUIEventIPC.h` sanitizes the `KeyNameIndex` and `CodeNameIndex`. Original Revision: https://phabricator.services.mozilla.com/D286456 Differential Revision: https://phabricator.services.mozilla.com/D286586
Original Revision: https://phabricator.services.mozilla.com/D286003 Differential Revision: https://phabricator.services.mozilla.com/D286615
…on has no segments. a=RyanVM DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D284193 Differential Revision: https://phabricator.services.mozilla.com/D286956
…gainst it. a=RyanVM DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D284178 Differential Revision: https://phabricator.services.mozilla.com/D286949
Differential Revision: https://phabricator.services.mozilla.com/D285582
Differential Revision: https://phabricator.services.mozilla.com/D285584
…ible. a=RyanVM Original Revision: https://phabricator.services.mozilla.com/D283215 Differential Revision: https://phabricator.services.mozilla.com/D287058
Original Revision: https://phabricator.services.mozilla.com/D286357 Differential Revision: https://phabricator.services.mozilla.com/D286710
…M DONTBUILD Original Revision: https://phabricator.services.mozilla.com/D286362 Differential Revision: https://phabricator.services.mozilla.com/D286754
Differential Revision: https://phabricator.services.mozilla.com/D286343
Original Revision: https://phabricator.services.mozilla.com/D283899 Differential Revision: https://phabricator.services.mozilla.com/D287154
Differential Revision: https://phabricator.services.mozilla.com/D287072
Original Revision: https://phabricator.services.mozilla.com/D285035 Differential Revision: https://phabricator.services.mozilla.com/D287071
…alue of the contentType header a=pascalc Differential Revision: https://phabricator.services.mozilla.com/D287086
Original Revision: https://phabricator.services.mozilla.com/D283332 Differential Revision: https://phabricator.services.mozilla.com/D287194
…_REUSE on MacOS. a=RyanVM MacOS Tahoe has a bug where (very intermittently) pages can be zeroed by the kernel after going through `madvise` with `MADV_FREE_REUSABLE` and then `MADV_FREE_REUSE`. The fuzz bug triggers this issue in the JS shell and we've also seen an increase in crashes on Mac after the release of Tahoe, with very similar signatures. I've been able to reproduce this with a stand-alone C++ test case and the issue has been reported to Apple. I haven't been able to reproduce this bug with `MADV_FREE` so this patch switches back to that, reverting bug 1567366 and bug 1682947. Unfortunately this means our RSS numbers are likely to increase. The JIT code allocator also uses `MADV_FREE_REUSABLE` and `MADV_FREE_REUSE` but it's more complex and it's not clear if it's affected the same way, so let's start with the GC memory allocator and see what the effect is on crash rates. Original Revision: https://phabricator.services.mozilla.com/D285226 Differential Revision: https://phabricator.services.mozilla.com/D286611
…scalc Original Revision: https://phabricator.services.mozilla.com/D285413 Differential Revision: https://phabricator.services.mozilla.com/D287180
…processes. a=pascalc Original Revision: https://phabricator.services.mozilla.com/D285125 Differential Revision: https://phabricator.services.mozilla.com/D287293
…content processes. a=pascalc" DONTBUILD This reverts commit 6ffa1bc.
…processes. a=pascalc Original Revision: https://phabricator.services.mozilla.com/D285125 Differential Revision: https://phabricator.services.mozilla.com/D287293
…ions. a=RyanVM Original Revision: https://phabricator.services.mozilla.com/D285170 Differential Revision: https://phabricator.services.mozilla.com/D286976
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.