proog128
Chrome Installed Extension Opener
https://www.dropbox.com/s/vf7w8oos1zxdhth/ExtensionOpener.zip?dl=0
Here's my first little app! Drag win32.js on to jswin to start it. It lists the installed extensions in Chrome for the selected profile and then you can double click the extensions name to open its folder. I made this a couple of years back in Lazarus and thought it'd be a nice simple thing to convert to JS Win. Works great...but, if you switch between profiles alot the memory usage goes up and up till it reaches about 30 meg and then it stays around that (goes up and down but stays around 30). I'm definitely to blame for some of that, I haven't tried in the slightest to be smart with memory usage. I open files and redo stuff everytime you change profiles. This was deliberate when I first made it so that I could keep it open and refresh it when needed. Plus I do have a butt load of extensions installed, most are disabled, I just keep them around for when I want to look at their code. But I do like the fact it only goes to 30 and then the gc must kick in or something. Talking of which, I wonder if it would help if you exposed the ability to call the gc..... http://stackoverflow.com/questions/10719967/v8-manually-initiate-the-garbage-collector Im going to leave it open for a while now while I have some tea and much some shows and see if it goes down over time.
I hate the way Ive done a bunch of this code (screw you styles!), but it was a learning experience and I think I know how to do some it better next time.....and there will be a next time. Going to do something else for a bit as I made a promise to help someone, so Im off to learn CouchDB and then Ill be back to make something with the gdi.
Thanks again for making this, look forward to wasting even more hours (I dont code easy) of my life on it!
Memory usage is completely controlled by the garbage collector at the moment. Furthermore, callback functions eat a lot of memory, because each callback pointer needs a full page (4 KB) in the current implementation. I will try to improve that in the future, but the memory management is a bit complex at this point. I will also add the possibility to manually trigger the garbage collector via a JavaScript call.
