Antoine Bluchet

it's ment to work in FF and chrome, at least the watch part.

+1 https://github.com/Seldaek/monolog/issues/206 https://github.com/ccampbell/chromelogger/pull/23 https://github.com/Seldaek/monolog/issues/172 : > Researched it a bit and I patched it, chrome seems to have a limit of 256KB across all headers, so splitting it like firephp...

`{detached: true` should get rid of this error but it is not available for cluster.

Because we can't get `detached: true` in cluster?

Yes ok so if that's the main reason, the only solution is to port cluster into pm2 instead of using the nodejs cluster. Did you try a simple cluster implementation...

@centigrade-thomas-becker you should try to use `child_process.spawn` and add a `{detached: true}` option.

May you try development branch @milichev ?

This should be fixed in nodejs then no?

> And why was this issue closed? After updating to pm2 3.0.0, I still have the same issue... Mhh did you update pm2 in memory? the `windowsHide` feature added in...

> It was closed cause we merged a PR which try to fix this issue. We were waiting for feedback about it. Shouldn't we document that when using a child...