zkPrograms using `SelfProof` gets stuck in the compilation step in the browser

[vale bramble]

Facing this issue with the latest o1js versions. I narrowed the problem to this

export const TestZkProgram = ZkProgram({
  name: 'TestZkProgram',
  publicInput: Field,
  publicOutput: Field,
  methods: {
    add: {
      privateInputs: [SelfProof],
      async method(a: Field, b: SelfProof<Field, Field>) {
        return a.add(b.publicOutput);
      },
    },
  },
});

the above zkProgram compiles in a node environment, but when tried to compile in browser it gets stuck, with no errors in console log. :/

[vivid lodge]

Is there anything else you are compiling before it? eg smart contracts that may consume memory?

[opaque dagger]

Which framework are you using?

[vale bramble]

No, only the ZkProgram.
In browser memory usage seems normal, (25mb - 50mb)

[vale bramble]

You mean web, framework?
I am using sveltekit.

[fickle ether]

For some reason, I see the difference in the behavior on the local and deployed versions of the frontend; probably it is related to CORS issues.

In such cases, I just deploy the frontend to the site and then debug the deployed version.

Also, this can happen if RSS memory is low.

[vale bramble]

tested in vercel, same issue.

[maiden cedar]

What adapter are you using? And do you have SSR and prerendering turned off? I've used SK in the past but sometimes it takes some massaging...

[vale bramble]

default ones

/** @type {import('@sveltejs/kit').Config} */
const config = {
    preprocess: vitePreprocess(),
    kit: {
        adapter: adapter()
    }
};

Let me try using react.

[vale bramble]

With react/next also, the compile step gets stuck

[thick palm]

Have you tried to prepare and use the contract cache?

[vale bramble]

Yeah, from the logs, after finding 3 things from cache, it stops.

[fickle ether]

Can you try this config
https://github.com/dfstio/web-mint-example/blob/main/next.config.mjs
and make sure that you use last version of the TypeScript and "use client"