[Webkit-unassigned] [Bug 86044] New: Web Inspector: tracking of FileSystem API reads/writes seriously hinders inspector usability
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed May 9 17:15:30 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=86044
Summary: Web Inspector: tracking of FileSystem API reads/writes
seriously hinders inspector usability
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: benvanik at google.com
CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
pmuellr at yahoo.com, joepeck at webkit.org,
pfeldman at chromium.org, yurys at chromium.org,
bweinstein at apple.com, apavlov at chromium.org,
loislo at chromium.org
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.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list