Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Stan who wrote (98044)	9/22/2017 10:44:43 PM
From: SI Ron (Crazy Music Man)	1 Recommendation Recommended By goldworldnet Respond to of 110626

Here is mine on FF, SeaMonkey and Chrome. (Win 7 Pro)

To: Stan who wrote (98044)	9/23/2017 12:03:15 AM
From: SI Ron (Crazy Music Man)	Read Replies (1) \| Respond to of 110626

Looks like a memory leak of some kind.

To: Stan who wrote (98044)	9/24/2017 10:05:15 AM
From: GPL	5 Recommendations Recommended By B.K.Myers Breccia Gottfried shadowman Stan Read Replies (1) \| Respond to of 110626

I am not sure if you have resolved your memory issue yet but, if not, you can use chrome's task manager to determine which resource is the major memory hog. In chrome, click the button (triple vertical dots) for the drop down menu found to the far right of the address bar, then select More tools/Task manager (or just type Shift + Esc). The chrome task manager displays resource information (task names, memory, cpu) for currently running chrome extensions, tabs, etc.