Skip to content

Failure to parse Firefox error #131627

Closed

Description

@polina-c

The bug blocks cl/551925539 that blocks #130354 that blocks flutter/devtools#3951

Flutter seems to fail parsing Firefox of new version:

Assertion failed: "Expected wrapException@http://jfbxk5-20020a056670ad0500b00884f10d5997.prod.google.com:20563/mobile/flutter/samples/hello_flutter/app/integration_test/integration_tests_screendiff_test_testing_web_browsers_firefox_linux_v85_0_firefox-linux_dart2js_canvaskit_web_test.dart.dart2js.browser_test.dart.js:5864:43 to match RegExp/^(.+) (\\d+):(\\d+)\\s+(.+)$/."
** Note that stack traces are truncated. See [http://go/dart-chain-stack-traces](https://www.google.com/url?q=http://go/dart-chain-stack-traces&sa=D) for information on how to view the full stack trace **
g3-root/third_party/dart_lang/v2/sdk/lib/_internal/js_runtime/lib/js_helper.dart 1195:37   wrapException
g3-root/third_party/dart_lang/v2/sdk/lib/_internal/js_runtime/lib/js_helper.dart 2698:3    assertThrow
g3-root/third_party/dart_lang/v2/sdk/lib/internal/iterable.dart 393:20                     moveNext
g3-root/third_party/dart_lang/v2/sdk/lib/internal/iterable.dart 871:12                     moveNext
g3-root/third_party/dart_lang/v2/sdk/lib/_internal/js_runtime/lib/core_patch.dart 476:5    _of
g3-root/third_party/dart_lang/v2/sdk/lib/_internal/js_runtime/lib/core_patch.dart 457:39   of
g3-root/third_party/dart/flutter/lib/src/foundation/stack_frame.dart 73:5                  StackFrame.fromStackString

assert(match != null, 'Expected $line to match $parser.');

Activity

  1. polina-c commented on Jul 31, 2023

    @polina-c
    ContributorAuthor

    G3 specifics: b/293925200

  2. darshankawar commented on Aug 1, 2023

    @darshankawar
    Member

    I tried to replicate it using integration_test example with updated Firefox version using latest chromedriver to run, but was unable to replicate it. I got below logs in the console. Most probably I might have missed some steps to properly replicate it, but based on the report, labeling for team's attention.

    dhs@Dhss-MacBook-Pro chromedriver_mac64 % ./chromedriver --port=4444
    Starting ChromeDriver 114.0.5735.90 (386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}) on port 4444
    Only local connections are allowed.
    Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
    ChromeDriver was started successfully.
    [1690877617.123][WARNING]: This version of ChromeDriver has not been tested with Chrome version 115.
    [1690877740.302][WARNING]: This version of ChromeDriver has not been tested with Chrome version 115.
    [1690877905.369][WARNING]: This version of ChromeDriver has not been tested with Chrome version 115.
    [1690877982.664][WARNING]: Chrome's trace buffer filled while collecting events, so some trace events may have been lost
    [1690877983.664][WARNING]: Chrome's trace buffer filled while collecting events, so some trace events may have been lost
    [1690877984.666][WARNING]: Chrome's trace buffer filled while collecting events, so some trace events may have been lost
    [1690877985.666][WARNING]: Chrome's trace buffer filled while collecting events, so some trace events may have been lost
    [1690877986.669][WARNING]: Chrome's trace buffer filled while collecting events, so some trace events may have been lost
    [1690877987.668][WARNING]: Chrome's trace buffer filled while collecting events, so some trace events may have been lost
    
    
    Screenshot 2023-08-01 at 1 49 50 PM
  3. added
    platform-webWeb applications specifically
    team-webOwned by Web platform team
    frameworkflutter/packages/flutter repository. See also f: labels.
    and removed
    in triagePresently being triaged by the triage team
    on Aug 1, 2023
  4. gspencergoog commented on Aug 1, 2023

    @gspencergoog
    Contributor

    Yes, I ran into this too when I was looking at why my memory leak fix was failing in Google tests.

  5. added
    r: fixedIssue is closed as already fixed in a newer version
    on Aug 3, 2023
  6. changed the title [-]Failure to parse FireFox error[/-] [+]Failure to parse Firefox error[/+] on Aug 14, 2023
  7. github-actions commented on Aug 28, 2023

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  8. locked as resolved and limited conversation to collaborators on Aug 28, 2023
  9. added
    a: leak trackingIssues and PRs related to memory leaks detected by leak_tracker
    on Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    a: leak trackingIssues and PRs related to memory leaks detected by leak_trackerbrowser: firefoxonly manifests in Firefoxframeworkflutter/packages/flutter repository. See also f: labels.platform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-webOwned by Web platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions