4 ms·

I'm not sure why you would think that? The issue described in this blog post is relating to the performance of a particular CSS selector that jQuery implements

by jeresig 16y ago

I'm not sure why you would think that? The issue described in this blog post is relating to the performance of a particular CSS selector that jQuery implements - not really anything having to do with memory usage (and the memory usage of jQuery certainly isn't anything significantly above-and-beyond what a normal web application would use).

leppie 16y ago
I was just wondering :) I am probably completely off target. Here is a screenie of what I get every morning. Chrome 9 now (same for 8). 1st col is pvt bytes, 2nd is working set: http://imageupload.org/?di=13129549812715 http://imageupload.org/?di=13129549812715 Edit: Interestingly after some usage, the memory gets freed, and it seems to return to normal again, ~50MB per tab. Edit 2: Now I seem to get some Flash not responding dialogs. Sorry, it seems more likely a Flash issue, although I dont even have any Flash open on any tab. Edit 3: Chrome stats: http://imageupload.org/?di=212954996318 http://imageupload.org/?di=212954996318. Seems there is a problem with GC being a 'tad' conservative.