Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.19.0 hangs after a sysctlbyname kern.nx warning

See original GitHub issue

Steps to reproduce

Tell us about your environment:

Puppeteer version: 1.19.0
Platform / OS version: Mac OS 10.14.5; Ubuntu Xenial on Travis CI
Node.js version: 8, 10, 12

Tested in both environments and the only working combination is Xenial + Node 12.

What steps will reproduce the problem? Running our test suite. I have tried to find minimal reproduction code without success. There are just too many variables. It runs just fine on previous versions of Puppeteer though.

What is the expected result? Puppeteer does not hang.

What happens instead? Promises from Puppeteer stop resolving and the script gets stuck. It does not appear to have anything to do with the code itself, because:

It always happens at a certain point in the code, after quite a lot of operations, where a page.*() is awaited. This page.*() function is never executed. I assume this because when page.evaluate() is used as the infringing function, its pageFunction has no effect in the browser.
When the infringing code is removed / commented out, the script continues fine, until it reaches another page.*() function and hangs again.
Once the next infringing function is removed, the script continues to the next function and so on.

Sadly, the only thing I was able to find now, is that there’s always a warning printed to the dumpio console when the script hangs.

From Mac OS:

[0730/111519.065822:WARNING:system_snapshot_mac.cc(42)] sysctlbyname kern.nx: No such file or directory (2)

Additionally, there’s this warning printed before the first one, but I feel it’s unrelated.

[0730/111518.892299:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffee8c41000, 0x2000): (os/kern) invalid address (1)

Sorry for skipping the line, but I wanted to bring this to your attention @aslushnikov, because the behavior is really weird and might be caused by some deeper rooted issue.

Issue Analytics

State:
Created 4 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

7reactions

TunedMidjacommented, Oct 18, 2019

I get the same error after upgrading macOS to Catalina. I’m not using any flags when starting Chrome. It happens when run tests in an Angular app using Karma. Any ideas what might cause this?

1reaction

ctcpipcommented, Oct 16, 2019

@knownasilya

https://bugs.chromium.org/p/chromium/issues/detail?id=982977 is the problem https://bugs.chromium.org/p/chromium/issues/detail?id=737678 shows the flag is not needed anymore anyway

Top Results From Across the Web

sysctlbyname for kern.osrelease returns NULL - Stack Overflow

It seems that sysctlbyname returns integer value and you try to return locally created char pointer from your function.

Search Results - CVE

The mission of the CVE® Program is to identify, define, and catalog publicly disclosed cybersecurity vulnerabilities.

View All Attachments for Bug 794232 - Gentoo's Bugzilla

Portage 3.0.19 (python 3.9.5-final-0, default/linux/amd64/17.1/desktop/gnome/systemd, gcc-11.1.0, glibc-2.33, 5.12.9 x86_64) ...

https://mirror.math.princeton.edu/pub/debian/dists...

Reported by Tran Tien Hung - CVE-2018-18344: Inappropriate implementation in ... Remove non-warning flags from the CFLAGS * Use a 60 second timeout...

https://reviews.freebsd.org/rP457024?diff=1

Users that experience hangs when starting X11 server, or observe (II) NVIDIA(0): ... Downgrade the Linux kernel version in /etc/sysctl.conf on FreeBSD ...