Leonid Romanovskii

@ponikrf and anyone hitting this, you can use [tiny-worker](https://github.com/avoidwork/tiny-worker), it appears to work fine with this and other native addons as a workaround until the `worker_threads` support is implemented

Second that windows 10, x64 tested on `0.49.0-beta1-sdk` and `0.48.3-sdk` log from `0.49.0-beta1-sdk`: ``` [7304:1052:0927/103603.533:FATAL:window_impl.cc(148)] Check failed: atom. : The parameter is incorrect. (0x57) Backtrace: v8::internal::TorqueGeneratedExportedMacrosAssembler::StoreSortStateTempArray [0x00007FFECD629132+9144722] v8::internal::TorqueGeneratedExportedMacrosAssembler::StoreSortStateTempArray [0x00007FFECD5B5612+8670834] v8::internal::TorqueGeneratedExportedMacrosAssembler::StoreSortStateTempArray...

@rogerwang Here is a sample that does it for me: [toaster.zip](https://github.com/nwjs/nw.js/files/5288933/toaster.zip) Steps to reproduce: 1. Navigate to the sample folder 2. `nw .` 3. Right click in the browser 4....

ok, i got something on this, it is related to #289 please refer to https://github.com/romgrk/node-gtk/issues/289#issuecomment-841063352 for how adding `console.log('whatever')` makes the gtk event loop issues weirdly go away when running...

apparently this is a recurring thing with native addons, so here's how people deal with it: folks over at https://github.com/andywer/threads.js/issues/334 use [tiny-worker](https://github.com/avoidwork/tiny-worker) instead of `worker_threads`, and it does appear to...

also apparently [tiny-worker](https://github.com/avoidwork/tiny-worker) uses [child_process.fork](https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options) under the hood, which i know is not a worker thread so not really a proper alternative to `worker_threads`, but i figured i'll post the...

I'll look into it, but i also have my hands full at the moment, so maybe later, the workaround will have to suffice for now

hey fellas, wanna see something freaky? 🥴 run this ```js console.log('bo!'); const WebSocket = require('ws'); const gi = require('node-gtk') const Gtk = gi.require('Gtk', '3.0') const socket = new WebSocket('wss://mppclone.com:8443/'); //...

I specifically use this to avoid the likes of qt's qode and yue's [yode](https://github.com/yue/yode), cause i run it on weird iot operating systems, and recompiling custom node versions for them...

@brandonpayton, in an array the commas are quite messy though, it does not look JSXy))