# Warning about Clone - Node Crash 'FATAL ERROR: v8::Object::SetInternalField() Internal field out of bounds'

**URL:** <https://discourse.nodered.org/t/warning-about-clone-node-crash-fatal-error-v8-setinternalfield-internal-field-out-of-bounds/16705>\
**Category:** General\
**Created:** [14 October 2019 18:01 UTC](https://discourse.nodered.org/t/warning-about-clone-node-crash-fatal-error-v8-setinternalfield-internal-field-out-of-bounds/16705 "2019-10-14T18:01:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![btsimonh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/btsimonh/32/3318_2.png) [@btsimonh](https://discourse.nodered.org/u/btsimonh)\
**Post date:** [14 October 2019 18:01 UTC](https://discourse.nodered.org/t/warning-about-clone-node-crash-fatal-error-v8-setinternalfield-internal-field-out-of-bounds/16705/1 "2019-10-14T18:01:22Z")

</div>

Had some fun with Node 12.10.0 and Node-Red 1.0.1 today.  
Again, [clone](https://github.com/pvorb/clone) comes back to haunt me.

Beware - if you have anything illicit in your messages (like a Pipe, or a Socket), you could end up with NodeJS crashing out because the message is not cloneable. (my issue was a ChildProcess).  
Node-Red at it's heart avoids cloning certain things (req and res, related to http) in messages - and the below PR could make that much easier in the NR code.

I've added a PR to clone to help control these kinds of issues, and to at least prevent crashes:

> <https://github.com/pvorb/clone/pull/108>

  
If you think they may affect you, please give it a smiley face!

---

<div class="post-metadata">

**Author:** ![btsimonh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/btsimonh/32/3318_2.png) [@btsimonh](https://discourse.nodered.org/u/btsimonh)\
**Post date:** [7 August 2020 08:10 UTC](https://discourse.nodered.org/t/warning-about-clone-node-crash-fatal-error-v8-setinternalfield-internal-field-out-of-bounds/16705/2 "2020-08-07T08:10:32Z")

</div>

latest one was a child process reference in a message :(.