Autoroll from main to 27.lts

[cobalt-github-releaser-bot]

Automated cherry-pick roll to 27.lts.

Original pull requests:

• media: Add page alignment and lockless decommit #11550
• Revert "android: Wait for media resources during shutdown (#11376)" #11564
• nplb: use SIGUSR2 in KillSendsSignalToSelf #11335

[github-actions]

🤖 Gemini Suggested Commit Message

---

cobalt: Roll main to 27.lts

Automated cherry-pick roll of changes from main to the 27.lts branch,
incorporating updates from pull requests 11550 and 11564.

This update simplifies the Android shutdown logic to improve restart
reliability and enhances the decoder buffer allocator with new
configuration options for page alignment and memory decommitting
to optimize overall system resource usage.

Bug: 11578

---

💡 Pro Tips for a Better Commit Message:

1. Influence the Result: Want to change the output? You can write custom prompts or instructions directly in the Pull Request description. The model uses that text to generate the message.
2. Re-run the Generator: Post a comment with: /generate-commit-message

[gemini-code-assist]

Code Review

This pull request removes the MediaResourceTracker utility and the kWaitForMediaResourcesOnShutdown feature across Android Starboard media components, and introduces a page alignment configuration (allocate_with_page_alignment) to the decoder buffer allocator strategy and StarboardMemoryAllocator. A critical bug was identified in JavaSwitches.java where generating separate --enable-features and --disable-features arguments for each switch will cause only the last occurrence to be preserved by base::CommandLine, silently ignoring the others. It is recommended to revert this change and continue joining the features with commas into single arguments.

[gemini-code-assist]

Critical Bug: Multiple --enable-features and --disable-features arguments are overwritten

In Chromium and Cobalt, base::CommandLine parses command-line arguments into a map where each switch key can only have a single value. If a switch like --enable-features or --disable-features is specified multiple times on the command line, only the last occurrence's value is preserved, and all previous ones are overwritten and ignored.

By changing the code to append separate --enable-features=... arguments for each feature instead of joining them with a comma into a single --enable-features argument, only the last enabled feature in the list will actually be enabled. All other features will be silently ignored.

Suggested Fix

Revert this change and continue to collect all enabled/disabled features using a StringJoiner (or List<String>) and append a single --enable-features=... and --disable-features=... argument to extraCommandLineArgs at the end of the method, for example:

public static List<String> getExtraCommandLineArgs(Map<String, String> javaSwitches) {
    List<String> extraCommandLineArgs = new ArrayList<>();
    StringJoiner jsFlags = new StringJoiner(";");
    StringJoiner enabledFeatures = new StringJoiner(",");
    StringJoiner disabledFeatures = new StringJoiner(",");

    if (javaSwitches.containsKey(JavaSwitches.USE_IPV4_FOR_DNS)) {
        enabledFeatures.add("UseIPv4ForDNS");
    }
    // ... collect other features ...

    if (enabledFeatures.length() > 0) {
        extraCommandLineArgs.add("--enable-features=" + enabledFeatures.toString());
    }
    if (disabledFeatures.length() > 0) {
        extraCommandLineArgs.add("--disable-features=" + disabledFeatures.toString());
    }
    return extraCommandLineArgs;
}