Yeah this looks like one of the nastier FI startup failures.
What is happening
FI/Tampermonkey can end up with an old or broken storage state where startup data becomes too large to pass through the extension runtime.
A common error in this situation is:
Code:
Message exceeded maximum allowed size of 64MiB
Important:
64 MiB is the runtime message limit, not the total IndexedDB storage limit.
So the database may contain much more than 64 MiB, but if Tampermonkey tries to transfer more than 64 MiB in a single internal message, Chrome rejects it.
The result is basically:
Code:
FI starts
→ loads saved state
→ Tampermonkey tries to transfer it
→ payload exceeds 64 MiB
→ runtime rejects it
→ FI initialization stops
→ UI never appears
This was especially possible with older
FI Library behavior when used without
FI Host, because image data could temporarily accumulate browser-side.
The important part is that FI's old temporary-storage recovery layer no longer exists in current builds.
So if the old Tampermonkey/FI state has already reached this condition, there isn't a reliable partial cleanup or migration path anymore.
The fix is a full reset.
- Back up any other Tampermonkey scripts you need.
- Completely uninstall Tampermonkey.
- Restart the browser.
- Install Tampermonkey again.
- Install the latest FI version from scratch.
- Do NOT restore the old FI storage/database.
If you use Tampermonkey sync, I also recommend temporarily disabling it while doing the clean install so the old state doesn't get restored automatically.
You can optionally give the fresh FI copy a different name:
Code:
// @name FREEInternet-Bypass - Clean
But changing the name alone is
not the fix the important part is removing the old Tampermonkey/FI state completely.
I'm really sorry about this one. It's one of the hardest FI failures because everything looks active from the outside while initialization is actually dying internally before the UI is created.
Newer FI versions have changed how this storage is handled specifically to reduce the chance of this happening again.
If it still happens after a completely clean reset, send me the browser version, Tampermonkey version, FI version, and the Console/runtime error and I'll investigate it.