allocation 0x00000000 already registered @ :l190 size 1610612736; now calling from :l

allocation 0x00000000 already registered @ :l190 size 1610612736; now calling from :l190 size 1610612736?

Getting this a lot is our webplayer error tracking built with 4.2.2

App seems to carry on afterwards, does anyone know whether this is for info or indication of a problem. It is raised as type Error.

Have not been able to find any info on it googling.

Have the same error reported by GameAnalytics. It smells like some memory problems. I have also noticed that Chrome hangs for 10-15 seconds after memory usage goes over 700m.