Chrome 65 doesn't start up under Fedora 27 (in VMWare Fusion 10 VM): "Fatal process OOM in insufficient memory to create an Isolate"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
STR
0. Run rr record google-chrome
I see the following in my setup:
$ rr record google-chrome
...
shared memfd open() failed: Function not implemented
#
# Fatal process OOM in insufficient memory to create an Isolate
#
Nothing happens after the final message.
@rocallahan says that the shared memfd open() message is probably pulseaudio and can be ignored.
I tried increasing the RAM allocated to the VM to 8GB, and VRAM to 2GB (max Fusion allows), but same symptom. Seems to be an rr/Chrome issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running rr record google-chrome in the reported Fedora 27 VM under VMware Fusion 10 and confirm the Fatal process OOM output. Investigate whether the failure belongs to rr or Chrome, using the ignored shared memfd open() message as context; done means startup works under rr or the responsible component and reproducible cause are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100