tbh, the only way to capture the output on that platform I know of is running chrome in visual studio... I'll ask around to see whether there's a better solution
On Wed, Oct 7, 2015 at 4:06 PM PhistucK <[email protected]> wrote: > Windows 7. > > > ☆*PhistucK* > > On Wed, Oct 7, 2015 at 4:51 PM, Jochen Eisinger <[email protected]> > wrote: > >> depends a bit on the OS you run chromium on? >> >> On Mon, Oct 5, 2015 at 6:55 PM PhistucK <[email protected]> wrote: >> >>> Sure, but how do I get the output of the extension process? By enabling >>> logging? >>> >>> >>> ☆*PhistucK* >>> >>> On Mon, Oct 5, 2015 at 12:52 PM, Jochen Eisinger <[email protected]> >>> wrote: >>> >>>> it would be interesting to have the output of the extension process >>>> when running chromium with --js-flags="--trace-gc --trace-gc-nvp" >>>> >>>> Please file a bug with this information on crbug.com/new >>>> >>>> On Sat, Oct 3, 2015 at 5:49 PM PhistucK <[email protected]> wrote: >>>> >>>>> Sorry for the cross post, I wanted your opinion before I file an >>>>> issue, because I am not sure where to file it. >>>>> >>>>> I installed Outlook.com notifier >>>>> <https://chrome.google.com/webstore/detail/mkmomflkhdooajekmffpilpoenndjppk?utm_source=chrome-app-launcher-info-dialog> >>>>> and >>>>> recently, I found out it was using a lot of memory. >>>>> >>>>> Looking into it, it uses YUI to fetch mail.live.com, YUI adds the >>>>> content to a DocumentFragment, the script looks for an element, gets its >>>>> content and that is it, every half a minute or so. >>>>> >>>>> Using the Developer Tools feature, I used the Profiler panel, took a >>>>> heap snapshot, switched to the Containment view and saw that GC >>>>> roots>Global handles uses over 300 MBs. It basically contains the string >>>>> content fetched from mail.live.com ever since Chrome was started. >>>>> >>>>> I then went to the TImeline panel and clicked on the trash can button >>>>> ("Collect garbage"), took another heap snapshot and it went back to about >>>>> 1 >>>>> MB. >>>>> >>>>> I think I noticed that when the available memory is low, it does >>>>> collect the garbage quickly, but it happened when I artificially created >>>>> 1000 large DocumentFragments, added them to an array and deleted the >>>>> array. >>>>> >>>>> Should I file a V8 issue, or a Chromium issue? >>>>> I figure it is a V8 issue, but I want to make sure, since it does >>>>> involve extensions (a background page) and DOM operations. >>>>> >>>>> >>>>> >>>>> ☆*PhistucK* >>>>> >>>>> -- >>>>> -- >>>>> v8-users mailing list >>>>> [email protected] >>>>> http://groups.google.com/group/v8-users >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "v8-users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> -- >>>> Chromium Discussion mailing list: [email protected] >>>> View archives, change email options, or unsubscribe: >>>> http://groups.google.com/a/chromium.org/group/chromium-discuss >>>> >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
