-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger causes alt to crap out when JSON.stringify fails #17
Comments
I've hit the same issue once or twice. I'm inclined to agree with 1), because I don't think it's in any way mandatory to get the payload into the devtool. It's NICE of course but no need to halt the app. |
@goatslacker Can you compile the crx with this fix? Or describe a away to create crx from sources? |
This would be nice! I've just manually patched this in to the extension source, and then promptly forgot about it. Which means it'll break whenever I reinstall for some reason... |
👍 I'll amend with @jareware's patch |
Patched and released. |
I have a data structure being passed through the dispatcher that contains circular references (third party library, don't ask). When the chrome debugger is enabled a call to
JSON.stringify
, the following error is raised and alt fails to dispatch the event:The code in which it fails is:
So I think there are two problems:
The Chrome debugger hook should probably just log any failures but allow the dispatch to continue.
The stringify should handle circular refs. See this stack question for a way to do that: http://stackoverflow.com/questions/11616630/json-stringify-avoid-typeerror-converting-circular-structure-to-json
The text was updated successfully, but these errors were encountered: