Re: Stack Overflow
Re: Stack Overflow
- Subject: Re: Stack Overflow
- From: "Stockly, Ed" <email@hidden>
- Date: Wed, 12 Nov 2014 23:37:18 +0000
- Thread-topic: Stack Overflow
That's helpful. I always have only two tabs open. There seems to always be 4
Chrome helpers open at any time.
I use Application Monitor, but can't really use it in this case beyond real
time viewing, which doesn't help much. These macs are running 24 hrs a day
and the stack overflows generally occur once or twice a day.
I need an automated way to trap this error.
On 11/12/14 3:35 p.m., "Alex Zavatone" <email@hidden> wrote:
> Not sure if Google Chrome is like Safari in that respect, but Safari has
> changed its model from one big chunk of memory allocated to Safari process and
> another to handling the web content process to a separate process for each
> webKit instance. One process per browser view running. Add up the number of
> running web views across all your tabs and windows and you have the number of
> application processes dedicated to Safari IIRC. There may be some sort of
> limit here, but you get my point.
>
> You can also get real time feedback by launching the Application Monitor and
> displaying the main window. You can then filter by process name and you can
> follow the memory usage of just the google processes.
>
> Hope this helps.
> Alex
>
> Sent from my iPad. Please pardon typos.
>
> On Nov 12, 2014, at 4:22 PM, "Stockly, Ed" <email@hidden> wrote:
>
>> Thanks Alex, that's helpful.
>>
>> So this is interesting. I immediately restarted the script and after a few
>> minutes I get what's below. Suddenly there are four versions of Google
>> Chrome Helper running, each with a lot of memory being used. If I quit
>> Google Chrome, the helpers disappear, if I relaunch, two show up
>> immediately, two more a bit later, then each item I run the shell script,
>> the memory allocation for the helpers goes up. Some of the others change up
>> and down, but the helpers only go up.
>>
>> Hmmm... It would be pretty easy to parse that result and when the RSS for
>> any of the Google Chrome Helpers reach some number, to quit and relaunch
>> Chrome. I could also use UI Browser to identify when the error message
>> appears, to figure out what the safe upper limit of memory for those is.
>>
>> Thanks for the help guys, if you see any problems with that kind of
>> strategy, let me know!
>>
>> " PID RSS COMMAND
>> 412 138500 Google Chrome Helper
>> 226 138192 com.apple.IconServicesAgent
>> 410 137408 Google Chrome Helper
>> 404 120428 Google Chrome Helper
>> 111 111664 mds_stores
>> 402 86648 Google Chrome
>> 413 76448 Google Chrome Helper
>> 180 71416 ScreensharingAgent
>> 368 45044 AppleScript Editor
>> 103 37416 WindowServer
>> <snip>
>>
>>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden