search

ScottHamper / Cookies

JavaScript Client-Side Cookie Manipulation Library
The Unlicense
1.77k stars 169 forks source link

"Aw, Snap!" Error in Google Chrome #43

Closed matiasdecarli closed 9 years ago

matiasdecarli commented 9 years ago

Since i've started using this plugin, I'm seeing more and more this screen. Is there any known issue that causes this?

screen shot 2015-04-28 at 08 50 16

Once it happens, I have to close & open the tab again. Refresh doesnt work.

Thanks in advance

ScottHamper commented 9 years ago

Nope! No known issue. Cookies.js isn't really doing a whole lot, either, so I am skeptical that the issue is actually being caused by the library (unless it's some weird interaction with another third party thing).

If you find a reliable way to reproduce an issue, let me know!

markcellus commented 9 years ago

I'm actually experiencing this too. And only thing I've changed before seeing it is start using this library. I'll investigate further....

markcellus commented 9 years ago

Hey @matiasdecarli were you using browserify when you reported this issue?

matiasdecarli commented 9 years ago

@mkay581 Actually yes. I was using browserify. It seems like a very random thing. Did you discover anything?

markcellus commented 9 years ago

Yeah it looks like its related to requiring the lib via browserify/commonJS:

var Cookies = require('cookies-js');

Still investigating though... will report back here when done.

markcellus commented 9 years ago

Thanks @ScottHamper for reopening, although didn't really want to officially re-open until I confirm what the issue is. @matiasdecarli I haven't had much time to look at it since my last message. Sorry. I work for an agency so I pretty much have no time to do anything else lol. I'll see if I can look at it more closely over the weekend.

matiasdecarli commented 9 years ago

I believe this issue appears when you have the web developer tools open

markcellus commented 9 years ago

Yeah, doesnt look like this is an issue with the package. Looks more like an issue with Chrome dev tools (when you have the console open on the "Cookies" tab).

ScottHamper commented 9 years ago

Ok, thanks for looking into this, guys!

I'll go ahead and close the issue, but if you discover anything new we can always reopen again.

markcellus commented 9 years ago

No problem. Surprisingly, it appears to have been a bug that now seems to be fixed in latest Chrome browser. heh.

ScottHamper commented 9 years ago

Sweet! Glad to hear