What's the go with the GC these days?

Patrick Schluter Patrick.Schluter at bbox.fr
Mon Jan 7 07:35:01 UTC 2019


On Monday, 7 January 2019 at 06:52:40 UTC, H. S. Teoh wrote:
> On Sun, Jan 06, 2019 at 07:34:41PM -0800, Walter Bright via 
> Digitalmars-d wrote:
>> [...]
>
> I've experienced a similar effect in Firefox, and though I 
> cannot say for sure it isn't a GC problem, I notice that it 
> causes a long spike of intensive I/O, and appears to be 
> correlated with occasional segfaults and signs of memory 
> corruption / memory leak, and generally happens only after 
> significant usage over a prolonged timeframe, generally ending 
> up in a state of extreme memory usage (several GBs in resident 
> set size for just a small number of persistent tabs) that reset 
> to more reasonable levels upon restarting and restoring exactly 
> the same tabs.
I have that too. It happens always on javascript heavy pages like 
facebook or youtube. Killing the process with the taskmanager is 
the quickest way to resolve the issue.


More information about the Digitalmars-d mailing list