Why do prims sometime spring back to the old size when editing?

I've noticed this from time to time (perhaps a little more with the current client, but that may be my imagination)

Just tonight I made a box 1m x 1m x 0.1m

I realised I wanted it 0.01m thick, so I changed it. It then sprung back to 0.1m thick!

I edited it about 5 or 6 times and ever time it sprung back after the size editing.

Finally is stuck, and held the new size.

Odd !!!!

I guess I'm not alone in seeing this sometimes?

LAGZ!!!

Really. It's something to do with the sim and/or asset servers getting all lagzy and sending you old copies of the object. Drives me nuts when it happens.

There can be a bunch of causes, usually connectivity related, but the end result is your local cache is out of sync with the sim. Your local viewer knows you made an adjustment, but the sim didn't quite get the message. The next time the data is refreshed, the sim's version overrides, and the prim appears to spring back to its previous size.

For reasons no one has ever really been able to explain, sometimes a prim will "rot", meaning the discrepancy becomes irreversible. You can adjust its size a thousand times, and it will spring back a few seconds later each time. When that happens, the only fix is to shift-drag the prim to leave a copy in its place, and then delete the original. Usually the copy will behave properly.

this has been happening quite a bit to me lately, i did find a workaround that seems to help.
this seems to happen most often when using the arrows to increase or decrease a dimension, when that happens i find that if i actually type in the dimension i want into the little window then click off it the prim will hold the shape.

This is also a reported problem with the Nicholaz viewer, but I believe it happens with others too, especially in the case of resizing multiple prims, the viewer will sometimes let you go a hair beyond the normal size limits of a prim (I think I've seen it with link distances too) and snap back when you let go and the server autocorrects the new size.

othe things as mentioned can also happen

nicks viewer can be particulary annoying in this respect, since you can take some to the edge of the limit (not past) and have this happen (some kind of rounding error perhaps?) doesn't happen all the time.