Originally Posted by MrAlex
The number is an endian. It seems that if you have two startup caches (I'm guessing you have both FF and WF installed?) this problem occurs, although I'm not sure why. I'll try and look into it. Have you delete both files? Does the error definitely occur after?
The bug appeared while I only had WF installed.
There are never two caches at the same time. FF will replace the WF file and vice versa.
The browser will delete the current file once it has loaded, and generate a new one on exit.
Loading using the faulty file will not delete it, since it seems to get stuck before getting there.
If I delete the file WF will run.