... ever 10 until 20 Seconds for 1 or 2 Seconds and show this in Picture ! What is that ?



<--- the Number is always random ...

This means it cleans memory. How many RAM GB do you have? And who knows may be a client memory leak.

AFAIK you should run `gc.buffer 2048` and this should fix it

it's nothing to do with "how much " ram you have........
The machine I run has over 80 GB REAL ram available & is utilising ZERO swap........ and it STILL continually does this.

I reported it to  FP to get a  bootup fix so many times it is not funny.......

they seem to have done a partial fix, in that now when it reports it , it does not totally freeze the machine .

then in the console log it says :

[GC] Emergency garbage collection: 257 MB
[GC] Emergency garbage collection: 262 MB
[GC] Emergency garbage collection: 260 MB
[GC] Emergency garbage collection: 257 MB
[GC] Emergency garbage collection: 261 MB
[GC] Emergency garbage collection: 258 MB
[GC] Emergency garbage collection: 261 MB
[GC] Emergency garbage collection: 258 MB
[GC] Emergency garbage collection: 264 MB
..... texns of times.........
[GC] Emergency garbage collection: 258 MB
[GC] Emergency garbage collection: 257 MB

As I've said set gc.buffer to something higher than 256 and it won't collect GC like that

makes NO difference it STILL shows the GC warnings on screen  in bottom left.............

So is it saying that on clientside or serverside and where did you set the gc.buffer

... then i think, its a anoying bug !

it shows on the client side......(that's what Benny was talking about...)
also gc.buffer  seems not to be sticky on client