FRepLayout: History overflow, forcing history dump - meaning?

Hi,

In my server logs, I’m seeing log event like:
[2015.11.11-20.28.47:170][697]LogRep:Warning: FRepLayout::UpdateChangelistHistory: History overflow, forcing history dump MyPawn_C

Can someone explain me how to fix this and avoid to have those warning?

Thanks,

wanna push this, cuz I have the same issue

Great to know that I’m not alone ^^

Epic, could you please give the signification of this warning?
thanks,

Anyone can help to understand this warning?

Hi Elvince, I cannot replicate unfortunately what exactly I have done, but the error seems to be not appearing anymore for me. I had some other bugs as well that I was working on and at some point it just kinda solved itself. But I still wanna push this to see the concrete solution if someone comes up with it.

bumping this. i’m having the exact same issue in a project, rarely happens but when it does its for no apparent reason and nobody seems to know what this error means

Bumping this - getting this on a dedicated server build in 4.11 & 4.12.

FRepLayout::UpdateChangelistHistory: History overflow, forcing history dump

Its feels to be like some sort of infinite loop cutoff, the server halts for a second or 2 before resuming, and then this warning appears. Anyone know what causes this? Is it possible to have a recursive loop in replication?

This is because your actor has at least one replicated field’s buffer that is full (the max is 32 history records). Since network replication does not happen every frame, and if you update the replicated field’s value every tick, it will cause all the changes to be buffered, and the buffered record number could exceed the maximum buffer size. The engine simply gives you warning messages and will still process all the buffered history records which is a unnecessary work.

Please check if your field value is changed too frequently. To solve this problem, you can slow down the tick time, or use event-driven mechanism to update the field’s value. Hope it helps.

Thanks for the advice. Nex time I get this warning I will try it out :slight_smile:

Thanks for explanation. at least now I know what to look for.

That’s should be written in stone such explanation ^^ like a comment near the error message ^^