New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 877796 link

Starred by 1 user
Status: WontFix
Owner:
█ roc...@chromium.org
please use my google.com address
Closed: Aug 28
Cc:
pnangunoori@chromium.org
mac-bugs-priority@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: socketpair(AF_UNIX, SOCK_STREAM, 0, fds) == 0. : Too many open files (24) in pla

Project Member Reported by ClusterFuzz, Aug 25 
Detailed report: https://clusterfuzz.com/testcase?key=5740009643311104

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: CHECK failure
Crash Address: 
Crash State:
  socketpair(AF_UNIX, SOCK_STREAM, 0, fds) == 0. : Too many open files (24) in pla
  mojo::PlatformChannel::PlatformChannel
  content::internal::ChildProcessLauncherHelper::StartLaunchOnClientThread
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=570931:570951

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5740009643311104

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.

Comment 1 by pnangunoori@chromium.org, Aug 27

Cc: pnangunoori@chromium.org
Labels: M-69 Test-Predator-Wrong
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “platform_channel.cc” assigning to owner concerned from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/60f9ae4d892022f021c9d740dca8e2dd9efe1fc6

@rockot -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Comment 2 by roc...@chromium.org, Aug 28

Status: WontFix (was: Assigned)
Out of file descriptors, not something we can address.

Could indicate a FD leak somewhere in Chrome, but these reports don't make it any more likely it IF that's the case.
Project Member

Comment 3 by ClusterFuzz, Sep 4

Labels: Needs-Feedback
ClusterFuzz testcase 5740009643311104 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Comment 4 by roc...@chromium.org, Sep 4

Labels: ClusterFuzz-Ignore
►

Sign in to add a comment