Maximum call stack size exceeded

@markp – Thank you so much for your help and for digging into this before we could!

Hi @ZsPapp,

If you can provide more details about the dataset or the specific configurations used, it would help us better understand the root cause. If you share the exported dataset along with a copy of your upload plan, we can attempt to recreate this issue in several browsers and see if we observe the same behavior.

@markp shares our perspective on large data sets as well. We typically recommend splitting uploads into reasonably sized chunks whenever possible. This approach allows for faster validation, quicker uploads, and easier disambiguation, all of which are significant advantages.

Chrome and Edge both use the same underlying platform, known as Chromium. Since this serves as the foundation for both browsers, they share core features and functionalities, so it makes sense they are behaving similarly. You may want to try using Firefox for your upload as it may have a different restriction?

Thank you!