Skip to content

chromium terminated by signal SIGTRAP #3529

@Zebra2711

Description

@Zebra2711

OS/Platform

Arch Linux

Installed

Compiled from source

Version

v142.0.7444.59

Have you tested that this is not an upstream issue or an issue with your configuration?

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

can't run chromium

How to Reproduce?

.

Actual behaviour

.

Expected behaviour

.

Relevant log output

[3:3:0100/000000.845965:ERROR:content/zygote/zygote_linux.cc:633] Zygote could not fork: process_type renderer numfds 5 child_pid -1
fish: Job 1, 'chromium --user-data-dir …' terminated by signal SIGTRAP (Trace or breakpoint trap)
[3:3:0100/000000.846203:ERROR:content/zygote/zygote_linux.cc:665] write: Broken pipe (32)

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions