Open misterdev opened 8 years ago
Hmm, interesting. Thanks for reporting. I don't have easy access to OSX myself, so it's hard for me to reproduce. It would be nice if this could be narrowed down a bit to the piece of code that's responsible. Instructions for how to do that are here: https://developer.chrome.com/devtools/docs/javascript-memory-profiling
I use OSX at work, so I can't spend too much time every day doing tests, also this problem happens once a day after 3 or 4 hours of work. But I'll try to do some tests from tomorrow. Thanks for the documentation! I've just one question: I know how to use some of these tools on a web page, how can I inspect the PouchDB plugin inside the DevTools?
You can go to chrome://extensions/ , enable developer mode, then click 'background page'. (Not sure about the exact words, the Chrome on my pc isn't in English). Worth a shot.
Great! The words are correct, thanks.
It worked well today until I restarted my computer, I've seen that the RAM usage grows also if I'm not doing operations on the DB. I've recorded something from the Profile and Timeline tabs in the ChromeDevTools, you can find them here (https://drive.google.com/folderview?id=0B9FPm2zFS6ZzUTNuaDR1QXBDb3c&usp=drive_web) I'm not very familiar with these tools so I don't know exactly if I did something useful :D any tip is welcome.
Sometimes I get this message in the console.
I think this is the same as #14
I've noticed an high ram usage by this extension on Chrome 46.0.2490.86 (64 bit) on OSX El Capitain, When I kill the process, the PouchDB extension crashes or stops working.