Not responding on mac x64 - electron + prisma

[pruge]

• Electron-Builder Version: v22.14.5

• Node Version: v16.13.1

• Electron Version: v16.0.4
• Electron Type (current, beta, nightly): current

• Target: mac x64

I build @TasinIshmam's https://github.com/TasinIshmam/prisma-electron-test for mac x64. The build was successful. But when I run it it doesn't respond.

Strangely, it works fine when using lldb.

lldb dist/mac/my-electron-app.app/

This is part of the error report.

Date/Time:        2022-01-07 23:17:03.508 +0900
End time:         2022-01-07 23:17:23.420 +0900
OS Version:       macOS 11.6.1 (Build 20G224)
Architecture:     x86_64
Report Version:   32

Data Source:      Stackshots
Shared Cache:     165A35D0-A05F-3D15-AD2F-AA988AD43519 slid base address 0x7fff2000d000, slide 0xd000

Command:          my-electron-app
Path:             /Users/USER/Documents/*/my-electron-app.app/Contents/MacOS/my-electron-app
Identifier:       com.electron.my-electron-app
Version:          1.0.0 (1.0.0)
Parent:           launchd [1]
PID:              54379
Time Since Fork:  19s

Event:            hang
Duration:         19.91s
Duration Sampled: 1.10s (process was unresponsive for 19 seconds before sampling)
Steps:            11 (100ms sampling interval)

Hardware model:   MacBookPro10,1
Active cpus:      8
Boot args:        -no_compat_check

Time Awake Since Boot: 477678s
Time Since Wake:  62763s

Fan speed:        3669 rpm

--------------------------------------------------
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
--------------------------------------------------

Heaviest stack for the main thread of the target process:
  11  start + 1 (libdyld.dylib + 89917) [0x7fff20336f3d]
  11  ??? (my-electron-app + 3382) [0x10a18cd36]
  11  ElectronMain + 134 (Electron Framework + 105990) [0x111348e06]
  11  cdef_copy_rect8_16bit_to_16bit_sse4_1 + 10299641 (Electron Framework + 17651129) [0x1124045b9]
  11  cdef_copy_rect8_16bit_to_16bit_sse4_1 + 10297339 (Electron Framework + 17648827) [0x112403cbb]
  11  cdef_copy_rect8_16bit_to_16bit_sse4_1 + 10303019 (Electron Framework + 17654507) [0x1124052eb]
  11  cdef_copy_rect8_16bit_to_16bit_sse4_1 + 10304403 (Electron Framework + 17655891) [0x112405853]
  11  v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 5757322 (Electron Framework + 37143802) [0x11369b4fa]
  11  v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 5773995 (Electron Framework + 37160475) [0x11369f61b]
  11  v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 5759497 (Electron Framework + 37145977) [0x11369bd79]
  11  ElectronInitializeICUandStartNode + 871482 (Electron Framework + 977530) [0x11141da7a]
  11  ElectronInitializeICUandStartNode + 1471991 (Electron Framework + 1578039) [0x1114b0437]
  11  node::LoadEnvironment(node::Environment*, std::__1::function<v8::MaybeLocal<v8::Value> (node::StartExecutionCallbackInfo const&)>) + 109 (Electron Framework + 114606877) [0x11807b31d]
  11  node::EmitAsyncDestroy(node::Environment*, node::async_context) + 282491 (Electron Framework + 114899387) [0x1180c29bb]
  11  node::EmitAsyncDestroy(node::Environment*, node::async_context) + 283181 (Electron Framework + 114900077) [0x1180c2c6d]
  11  node::EmitAsyncDestroy(node::Environment*, node::async_context) + 278764 (Electron Framework + 114895660) [0x1180c1b2c]
  11  v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) + 689 (Electron Framework + 17996225) [0x1124589c1]
  11  v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) + 677 (Electron Framework + 19213093) [0x112581b25]
  11  ??? [0x4d0000a647]
  11  ??? [0x4d0000a91c]
  11  ??? [0x4d0000c921]
  11  ??? [0x4d0000c921]
  11  ??? [0x4d0000c921]
  11  ??? [0x4d0000c921]
  11  ??? [0x4d0000c921]
  11  ??? [0x4d0000c921]

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[mirukuz]

Can anyone follow up this issue?