3 ms·
Is all this just because they "lost control" of the old inspector to Google (who invested heavily in it)? The new one doesn't support the websocket protocol ye
by randallu 13y ago
Is all this just because they "lost control" of the old inspector to Google (who invested heavily in it)?
The new one doesn't support the websocket protocol yet so I can't use it in my WK stuff anyway, but I don't know why they spent a bunch of time on a new one. I was also sad to see the "Native Memory Instrumentation" removed from WebKit, because I've always wanted to know "where the memory goes" on any given page.
- huxley 13y agoFile a bug on this, it does sound like it shouldn't have disappeared like that.
- randallu 13y agoThe comment was that it was hard to maintain the way that it was written, which is probably true (there were hooks everywhere!). I don't know if there are any clever allocator/macro tricks you can use to know how many of each kind of object is allocated without a big perf hit.