Bug 123750 – Web Inspector: localStorage inspector very slow on big values

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector

[Derk-Jan Hartman]

Currently Wikipedia is testing caching JavaScript in localStorage.

In testing this, I noticed that trying to inspect localStorage using Safari becomes almost impossible. When trying to represent the value in the inspector, it seems to want to display the entire value in the row, which takes upto a minute.

The inspector should be smarter about this and recognize that a very big value is not fully suite to be represented like this, but should be shown using a file like representation.

[Radar WebKit Bug Importer]

<rdar://problem/15384930>

[Timothy Hatcher]

I agree, the current presentation does not live up how people are using LocalStorage now. Even the Inspector itself dumps large values into LocalStorage that it can't show. Detecting large values and letting you view them full-view would be great.

Thanks for the bug and Wikipedia test case!

[Derk-Jan Hartman]

still a problem

[Derk-Jan Hartman]

This seems possibly even worse in Safari 9 beta.

[Joseph Pecoraro]

Since DOMStorage has string keys/values how about we snip the strings to something like 50-100 characters.

Given:

    window.localStorage.key = "Really really really really really really long string";

The inspector could show something like:

    | "key" | "Really really really..." |

With some way to fetch the completely value. This is similar to RemoteObject previews, which abbreviates strings to 100 characters.

[Timothy Hatcher]

Sounds great to me!

[Derk-Jan Hartman]

This crash still happens, and it still annoys me about once a week, when I accidentally press the localStorage tab on a wikipedia and related websites.

[Joseph Pecoraro]

Created attachment 270954 [details]
[PATCH] Proposed Fix

[Joseph Pecoraro]

One thing worth considering is that we could have the backend truncate before sending to the frontend, avoiding sending megabytes of text over the protocol. However, we may want to update how we display things in the frontend, so this just leaves it a frontend decision to truncate for display only.

[WebKit Commit Bot]

Comment on attachment 270954 [details]
[PATCH] Proposed Fix

Clearing flags on attachment: 270954

Committed r196342: <http://trac.webkit.org/changeset/196342>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Derk-Jan Hartman]

Tested in nightly. Works like a charm !!
I'm super happy with this change, thx so much for listening.