question-mark
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.

[macOS / nw.js 0.42.5] "The display compositor is frequently crashing"

See original GitHub issue

NWJS Version : 0.42.5 SDK Operating System : macOS 10.14.6 (18G1012)

I can’t run any project, even the simpler Hello World code from the doc.

.
├── index.html
└── package.json
<!-- index.html -->
<!DOCTYPE html>
<html>
  <head>
    <title>Hello World!</title>
  </head>
  <body>
    <h1>Hello World!</h1>
  </body>
</html>
// package.json
{
  "name": "helloworld",
  "main": "index.html",
}

In the Terminal, I first cd in the app folder, and then call path/to/nwjs-sdk-v0.42.5-osx-x64/nwjs.app/Contents/MacOS/nwjs .

Actual behavior

Crash log:

[21848:35587:1129/224308.505703:FATAL:gpu_data_manager_impl_private.cc(986)] The display compositor is frequently crashing. Goodbye.
0   nwjs Framework                      0x000000011ac703f9 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15724985
1   nwjs Framework                      0x000000011ab92553 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 14816019
2   nwjs Framework                      0x000000011aba6649 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 14898185
3   nwjs Framework                      0x0000000118628a32 ChromeMain + 19862098
4   nwjs Framework                      0x0000000118625f9f ChromeMain + 19851199
5   nwjs Framework                      0x000000011862f454 ChromeMain + 19889268
6   nwjs Framework                      0x000000011842f0b3 ChromeMain + 17791187
7   nwjs Framework                      0x000000011848f003 ChromeMain + 18184227
8   nwjs Framework                      0x000000011848f2ac ChromeMain + 18184908
9   nwjs Framework                      0x000000011ac08baf v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15300975
10  nwjs Framework                      0x000000011ac1e551 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15389457
11  nwjs Framework                      0x000000011ac1e268 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15388712
12  nwjs Framework                      0x000000011ac85917 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15812311
13  nwjs Framework                      0x000000011ac1ee68 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15391784
14  nwjs Framework                      0x000000011abe6527 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15160039
15  nwjs Framework                      0x0000000118441a84 ChromeMain + 17867428
16  nwjs Framework                      0x000000011ac3b6fd v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15508669
17  nwjs Framework                      0x000000011ac7a957 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 15767319
18  libsystem_pthread.dylib             0x00007fff65af92eb _pthread_body + 126
19  libsystem_pthread.dylib             0x00007fff65afc249 _pthread_start + 66
20  libsystem_pthread.dylib             0x00007fff65af840d thread_start + 13
Task trace:
0   nwjs Framework                      0x000000011848eedb ChromeMain + 18183931
1   nwjs Framework                      0x000000011848ea80 ChromeMain + 18182816
2   nwjs Framework                      0x0000000118a35021 ChromeMain + 24107073
3   nwjs Framework                      0x000000011adec1d6 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 17280918
4   nwjs Framework                      0x000000011adcff9a v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 17165658
Task trace buffer limit hit, update PendingTask::kTaskBacktraceLength to increase.
IPC message handler context: 0xCC7D5A74

[1129/224308.511784:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffedfe37000, 0x2000): (os/kern) invalid address (1)
[1129/224308.595565:WARNING:system_snapshot_mac.cc(42)] sysctlbyname kern.nx: No such file or directory (2)
Trace/BPT trap: 5

Besides, the error message “The display compositor is frequently crashing. Goodbye.” feels a bit mocking 😄 Any suggestion? I’d really like to implement nwjs but I’m stuck in an embarrassing dead end. Thank you!

Davide

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
bastimeyercommented, May 9, 2020

The latest NW.js release (0.45.5) still has this problem. If a product_string value other than nwjs is set in the package.json, then the app will crash with “The display compositor is frequently crashing. Goodbye.”.

At first I thought this was because of some upstream Chromium changes caused by the lack of GPU acceleration in my macOS VMs, since code related to this error message has been changed recently in Chromium, but after checking everything Chromium related and almost giving up, I decided to look for issues here and found this thread. Should have done this sooner.

This issue is very unfortunate considering the product_string value needed for #7437, if your app building process doesn’t differ between macOS and Linux. Not that it’s impossible to work around this in the build process and fixing the macOS package.json, I’m just saying that it’s very unexpected that it only crashes on macOS.

0reactions
semmelcommented, Feb 23, 2022

It took me 3 hours to find product_string to be the reason for my crashes.

@rogerwang Please update Package and Distribution docs with a warning not to use it

Read more comments on GitHub >

github_iconTop Results From Across the Web

The display compositor is frequently crashing - Google Groups
I have been using nw.js very successfully for some time, both on Windows and Mac. I recently added code to my Windows project,...
Read more >
Understanding Crash Dump - NW.js Documentation
Once NW.js crashed, a minidump file ( .dmp ) will be generated on disk. Users can include it in the bug report. You...
Read more >
NW.js Page
Basically this page encapsulates some of the experience I have had with using NW.js. Preamble: Basically my coding started with 6800/6809 machine coding...
Read more >
homebrew-core - Homebrew Formulae
a2ps 4.14 Any‑to‑PostScript filter aacgain 1.8 AAC‑supporting version of mp3gain aalib 1.4rc5 Portable ASCII art graphics library aamath 0.3 Renders mathematical expressions as ASCII art
Read more >
fr2.rpmfind.net/linux/opensuse/tumbleweed/repo/oss...
Only display bulk unverified sessions nag when current sessions is ... Update bundled Python sysconfigs for Linux and macOS gh#PyO3/maturin#1355 ++++ ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found