Repository navigation
Uncaught hole #1143
Description
What is the current behavior?
Delete the last word in input field, the browser will blocking until raven-js throw Uncaught hole exception in below code:
try {
// 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.
return func.apply(this, args);
} catch (e) {
self._ignoreNextOnError();
self.captureException(e, options);
throw e;
}
What is the expected behavior?
Raven.js version: 3.20.1 and Using npm package.
browser: chrome
OS: MacOS, windows 10
React: 0.14.3
Hosted Sentry by ourselves (8.21.0)
Activity
kamilogorek commentedon Nov 21, 2017
Hey @WhatAKitty, can you provide a reproducible test case that we could use to test this behavior?
WhatAKitty commentedon Nov 22, 2017
@kamilogorek I cannot reproduce this in jsfiddle, but it actually happened in my workplace. And it still in there when I upgrade react to 0.14.9
WhatAKitty commentedon Nov 22, 2017
@kamilogorek I use html script import, the error changed to :
and this always happened while the input has an validation. And at same time, the browser will throw an error:
[Deprecation] 'window.webkitStorageInfo' is deprecated. Please use 'navigator.webkitTemporaryStorage' or 'navigator.webkitPersistentStorage' instead.jiananshi commentedon Jan 24, 2018
How abt your client environment? such as Chrome with several plugins on Mac OSX, information like these would be help, as far as I know there is no such
webkitStorageInfovariable use in raven-js, try another browser or use it in stealth mode see if it's reproduce.jutaz commentedon Jul 12, 2018
I recently encountered this in one of our apps. the cause was a big object, that had a bunch of circular references in it passed to a breadcrumb, and caused the
stringifyto fail, as it simply ran out of memory when trying to stringify such object.I may be able to recreate this in codepen or plunker, but the thing is - I'm not sure if that's something that can/would be fixed. One interesting way to fix this would be to limit the depth of the object passed in to say
10, which would, in some cases, prevent it from becoming too large.kamilogorek commentedon Sep 17, 2018
As we released Release Candidate of our SDK v4, we clean up some of the issues. Please feel free to let me know and I'll reopen this issue if this will ever happen in the new version. Cheers!
fix(deps): bump unhead 2.1.4 to 2.1.12 to fix CVE-2026-31860 and CVE-…
fix(deps): bump unhead 2.1.4 to 2.1.12 to fix CVE-2026-31860 and CVE-…