[chromium-bugs] Re: Issue 394296 in chromium: Hang bug in history.pushState()

[c***@googlecode.com]

Comment #4 on issue 394296 by ***@gmail.com: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

I found another case where this occurs:

If you write an endless recursion like following you will get the
error 'RangeError: Maximum call stack size exceeded ':

var endless = function() {
endless();
};

But not if you change this recursion to something with history.pushState:

var endless = function() {
history.pushState(undefined, undefined,
window.location.toString().split('#')[0]);
endless();
};
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #5 on issue 394296 by ***@gmail.com: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

I found another case where this occurs:

If you write an endless recursion like following you will get the
error 'RangeError: Maximum call stack size exceeded ':

var endless = function() {
endless();
};

But not if you change this recursion to something with history.pushState:

var endless = function() {
history.pushState(undefined, undefined,
window.location.toString().split('#')[0]);
endless();
};
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #6 on issue 394296 by ***@chromium.org: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

Issue 460291 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #8 on issue 394296 by ***@chromium.org: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

meacer@ - the problem isn't history limit, it doesn't actually go above 50.
The underlying issue is that the IPC queue doesn't have a limit, so we have
a TON of IPCs queued up because of the pushState call in a loop. It just
takes lots of CPU and time to process through the messages.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #12 on issue 394296 by ***@chromium.org: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

Issue 581237 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #13 on issue 394296 by ***@gmail.com: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

This bug was turned into a tool for trolls. They post links
(crashsafari.com, crashchrome.com) everywhere, from Twitter to Facebook.
Some even clone the JS code and/or obfuscate with URL shortening services.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #14 on issue 394296 by ***@gmail.com: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

Is it there any form to fix it? I can't use Chrome for more than 45
seconds. I tried erasing my history and that and it isn't possible because
Chrome crashes before it erases everything.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #15 on issue 394296 by ***@gmail.com: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

If Chrome crashes when it restarts, you can delete file "Current Tabs" in
your profile folder, or you can disconnect/disable the network.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #16 on issue 394296 by ***@chromium.org: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

Just tried it on Windows stable (32-bit)...Looks like it caused an OOM
crash in the browser process, after hanging for a bit.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #17 on issue 394296 by ***@gmail.com: Hang bug in
history.pushState()
https://code.google.com/p/chromium/issues/detail?id=394296

Reported Jul 16, 2014

so google, you had to wait one and a half until this turned into
abuse. "Thank you" for not giving a damn about it. now I've lost all my
history because of this.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings