search

nwjs / nw.js

Call all Node.js modules directly from DOM/WebWorker and enable a new way of writing applications with all Web technologies.
https://nwjs.io
MIT License
40.41k stars 3.88k forks source link

Some webviews are crashing when running in a VM #8047

Open mutlucan96 opened 1 year ago

mutlucan96 commented 1 year ago

Issue Type

Before opening an issue, please search and see if it has already been raised.

Please use our mailing list or Gitter chatroom to ask questions. The issue tracker is only for bugs and feature requests, in English only. Please note that issues without a repro or code snippet are less likely to be resolved.

Current/Missing Behavior

Some websites in webview crash randomly several webviews including itself. I experience this randomly, however, is guaranteed to cause a crash.

I did some research and I guess it's related to running a VM. Chromium looks for max_freq for CPU and it doesn't exists in VM environments. In fact, I'm running this on a VM. This problem doesn't happen with Chrome or Chromium, still in the same VM and OS.

Expected/Proposed Behavior

Additional Info

[0328/161914.189779:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0328/161914.189878:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Received signal 11 SEGV_ACCERR 3dac0d0000fb
#0 0x7fa987319573 (/home/mutlu/nwjs/lib/libnw.so+0x64c5572)
#1 0x7fa9873c77c1 (/home/mutlu/nwjs/lib/libnw.so+0x65737c0)
#2 0x7fa980c6fb20 (/usr/lib64/libc.so.6+0x3cb1f)
#3 0x7fa98a4d690c (/home/mutlu/nwjs/lib/libnw.so+0x968290b)
#4 0x7fa98a497581 (/home/mutlu/nwjs/lib/libnw.so+0x9643580)
#5 0x7fa98b0f4892 (/home/mutlu/nwjs/lib/libnw.so+0xa2a0891)
#6 0x7fa98af76172 (/home/mutlu/nwjs/lib/libnw.so+0xa122171)
#7 0x7fa98af74632 (/home/mutlu/nwjs/lib/libnw.so+0xa120631)
#8 0x7fa9866bbd57 (/home/mutlu/nwjs/lib/libnw.so+0x5867d56)
#9 0x7fa98af8fbcc (/home/mutlu/nwjs/lib/libnw.so+0xa13bbcb)
#10 0x7fa9866cfcf8 (/home/mutlu/nwjs/lib/libnw.so+0x587bcf7)
#11 0x7fa9866ddc8c (/home/mutlu/nwjs/lib/libnw.so+0x5889c8b)
#12 0x7fa9866ddde3 (/home/mutlu/nwjs/lib/libnw.so+0x5889de2)
#13 0x7fa98a4b201f (/home/mutlu/nwjs/lib/libnw.so+0x965e01e)
#14 0x7fa98a4b2a3f (/home/mutlu/nwjs/lib/libnw.so+0x965ea3e)
#15 0x7fa98a4b2af6 (/home/mutlu/nwjs/lib/libnw.so+0x965eaf5)
#16 0x7fa98737f41b (/home/mutlu/nwjs/lib/libnw.so+0x652b41a)
#17 0x7fa987396548 (/home/mutlu/nwjs/lib/libnw.so+0x6542547)
#18 0x7fa987395f0f (/home/mutlu/nwjs/lib/libnw.so+0x6541f0e)
#19 0x7fa987396ca5 (/home/mutlu/nwjs/lib/libnw.so+0x6542ca4)
#20 0x7fa987337f96 (/home/mutlu/nwjs/lib/libnw.so+0x64e3f95)
#21 0x7fa987396fdb (/home/mutlu/nwjs/lib/libnw.so+0x6542fda)
#22 0x7fa98735e1d1 (/home/mutlu/nwjs/lib/libnw.so+0x650a1d0)
#23 0x7fa98ca8f7e0 (/home/mutlu/nwjs/lib/libnw.so+0xbc3b7df)
#24 0x7fa9868aef2b (/home/mutlu/nwjs/lib/libnw.so+0x5a5af2a)
#25 0x7fa9868afdcd (/home/mutlu/nwjs/lib/libnw.so+0x5a5bdcc)
#26 0x7fa9868acfc5 (/home/mutlu/nwjs/lib/libnw.so+0x5a58fc4)
#27 0x7fa9868ad602 (/home/mutlu/nwjs/lib/libnw.so+0x5a59601)
#28 0x7fa9830ac2b9 ChromeMain
#29 0x7fa980c5a510 __libc_start_call_main
  r8: 0000000000000000  r9: 0000000000000001 r10: 0000000000000000 r11: 0000000000000000
 r12: 00007fa98d655660 r13: aaaaaaaaaaaaaaaa r14: 00003dac000031bd r15: 000056399d9256b8
  di: 000056399d8e2738  si: 0000000000000000  bp: 00007ffec3ee74e0  bx: 000056399d8e2530
  dx: 0000000000000000  ax: 000000000d0000f8  cx: 00003dac00000000  sp: 00007ffec3ee7480
  ip: 00007fa984663a39 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 00003dac0d0000fb
[end of stack trace]
ayushmanchhabra commented 1 year ago

I did some research and I guess it's related to running a VM. Chromium looks for max_freq for CPU and it doesn't exists in VM environments.

Chromium looks for max_freq for CPU which does not exist in VM environments and hence is expected to crash?

In fact, I'm running this on a VM. This problem doesn't happen with Chrome or Chromium, still in the same VM and OS.

But the problem/crash does not occur on Chromium/Chrome while running in VM environment?

Closing until issue is clarified.

mutlucan96 commented 1 year ago

Yes, the problem does not happen on Chrome or Chromium in the same VM. As I already stated before:

This problem doesn't happen with Chrome or Chromium

ayushmanchhabra commented 1 year ago

I guess I must have misread the issue. My bad