DataCloneError when capturing events with raven-js

[jharris4]

Do you want to request a feature or report a bug?

bug

(If this is a usage question, please do not post it here—post it on forum.sentry.io instead. If this is not a “feature” or a “bug”, or the phrase “How do I...?” applies, then it's probably a usage question.)

What is the current behavior?

raven-js throws a DataCloneError on Firefox iOS`

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.

What is the expected behavior?

raven-js should not throw errors :-)

Which versions of Raven.js, and which browser and OS are affected by this issue? Did this work in previous versions of Raven.js? Are you using the CDN (http://ravenjs.com)? Are you using hosted Sentry or on-premises? If on-premises, which version (e.g. 8.7.0)?

DataCloneError

The object can not be cloned.

./node_modules/raven-js/src/raven.js in this at line 360:0

Seeing this with:
Self-hosted sentry version 3.22.1
Firefox iOS 10.6
iOS 11.2.5

[kamilogorek]

Hey @jharris4, this is an error that can happen while working with WebWorkers or PostMessage calls, that are using structured cloning algorithm - https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm
Raven is using neither of them. Also when you take a look at line 360 that you provided, you can read:

 // Attempt to invoke user-land function
 // NOTE: If you are a Sentry user, and you are seeing this stack frame, it
 // means Raven caught an error invoking your application code. This is
 // expected behavior and NOT indicative of a bug with Raven.js.

Therefore, there's a very large chance that actually your code is trying to invoke the method that's causing this behavior :)

Can you past whole stack trace of the error with the snippets of code that's called?

Cheers!

[jharris4]

Hi @kamilogorek, I did notice the comment saying it was not indicative of a bug in Raven.js! ;-)

I decided to file a bug anyway, because the error was logged to Sentry by Raven.js and I figured this should be addressed somehow...

There isn't much else to the stack trace:

DataCloneError: The object can not be cloned.
 at postMessage([native code])
 at this(./node_modules/raven-js/src/raven.js:360:0)

Seems like something weird that is only happening with Firefox for iOS.

I've never personally used that browser, but one of our users apparently did...

[jharris4]

I was trying to search the web to find out what this error even means, and the only reference I can find is this one: https://stackoverflow.com/questions/42170826/categories-for-rejection-by-the-structured-cloning-algorithm

[kamilogorek]

I'll try to take a look at it sometime in the future. It'd be great if someone could be able to come up with a reproducible scenario.

[mscuthbert]

I’ve just started to get the same message on Raven from a windows 10 machine running Chrome 68. The full stack trace is:

DataCloneError: Failed to execute 'postMessage' on 'Window': function (a){if(qe.$a.hasOwnProperty(a))return qe.$a[a]} could not be cloned.
at _reportEvent (/:1:35800)
at eval (/:1:35800)
at eval (/:1:35800)

I’m not using WebWorkers at all in my code and don’t recognize the code as my own at all.

I did recently add code that had WeakMaps in it to my stack, and thinking from my experience in other languages I can imagine that WeakRefereces might cause errors in cloning, especially since WeakMaps and WeakSets don’t allow iterating.

[gmattar]

@mscuthbert I'm getting the same problem for a few days now. Did you have any luck debugging?

[Sija]

@mscuthbert Same here, I've got one yesterday (Chrome Version: 40.0.2214, Windows 7).
Full stacktrace below:

DataCloneError: Failed to execute 'postMessage' on 'Window': function (){var r,o,a=arguments[0],s=arguments[1],u="["+(e?e+":":"")+a+"] ",l=G(arguments,2).map(function(e){re...<omitted>...)} could not be cloned.
 at _reportEvent(/:1:35652)
 at eval(/:1:35652)
 at eval(/:1:35652)

[mscuthbert]

@gmattar unfortunately we only run Raven on our obfuscated, non-map code, so debugging will bee pretty hard, but it looks like we'd all need to get this working on non-minified raven to figure out what's up.