I'm not able to reproduce this behavior. I only get this behavior if I visit node/add/page and then re-open node/add/page from the admin menu (effectively opening the page twice in a row). I think this is the expected behavior in this case, since the previous page was node/add/page
Here is a sample module that does the required task.
https://github.com/stpaultim/field_change_log
I'm still working on it and testing it. But, initial tests are good. ...
Probably not the reason, but worth to do a quick check:
Sometimes the update cache interferes, so if something's odd with updates - some module (or core) claims to have updated, but then...
Comments
I'm not able to reproduce this behavior. I only get this behavior if I visit node/add/page and then re-open node/add/page from the admin menu (effectively opening the page twice in a row). I think this is the expected behavior in this case, since the previous page was node/add/page