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.

[v0.18.1] --single-process Seg Fault

See original GitHub issue

The following errors are displayed when I tried to add --single-process on the CLI or added on the chromium-args property:

[6680:6340:1020/112613:ERROR:proxy_service_factory.cc(127)] Cannot use V8 Proxy resolver in single process mode.
[6680:6340:1020/112613:ERROR:proxy_service_factory.cc(127)] Cannot use V8 Proxy resolver in single process mode.
[1020/112613:ERROR:process_reader_win.cc(233)] ReadMemory at 0xa399fbb of 512 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1020/112613:ERROR:crash_report_exception_handler.cc(98)] WriteEverything failed
Segmentation fault

Previous app worked with v0.17.3 but without the single process mode.

nwjs-sdk-v0.18.1-win-x64 Windows 7

Issue Analytics

State:
Created 7 years ago
Reactions:2
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

divinemanwahcommented, Oct 20, 2016

Update:

Tried again with the out-of-the-zip distribution (plain, no other codes involved), the following error still happens using --single-process:

$ nw --single-process
[6204:7408:1020/113834:ERROR:proxy_service_factory.cc(127)] Cannot use V8 Proxy resolver in single process mode.
[6204:7408:1020/113834:ERROR:proxy_service_factory.cc(127)] Cannot use V8 Proxy resolver in single process mode.
[6204:3996:1020/113835:ERROR:angle_platform_impl.cc(33)] ANGLE Display::initialize error 5: DXGI 1.2 required to present to HWNDs owned by another process.
[6204:3996:1020/113835:ERROR:gl_surface_egl.cc(612)] eglInitialize D3D11 failed with error EGL_NOT_INITIALIZED, trying next display type
Segmentation fault

0reactions

rogerwangcommented, Nov 1, 2016

This is fixed in git according to the crash dump and will be available in the next nightly build.