Indeed, that's a bug (or something bug-like) in Chrome v 35.
There's more info about the issue and workarounds here:
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community