In my application I am performing many small reads/writes from a Web Worker using the HTML5 File System API. I'm using the file system as a semi-persistent cache for binary data as one would use a scratch file in a native app. Recently the reads have started to get logged in the Inspector (at least in Chrome), and when the inspector is up my browser slows down to the point of being unusable. The culprit is the hundreds+ of 'Request URL:blob:http://....' logged bits in the Network panel of the inspector. Eventually the browser also consumes significantly more memory (as it's retaining every blob), making it difficult to track memory usage. Basically, with this feature it's now impossible to run my app with the inspector up. Can this be a setting that defaults to off? I am failing to see the immediate use of this information in complex applications that are doing anything more than reading text files, and it's seriously hindering my ability to develop my application. I can build a repro to see if the performance impact only occurs when the reads happen from a Worker, but whatever the decision is it should be consistent.
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests. Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.