I'm sorry to hear you're experiencing issues with exporting JSON in Spine 3.8 on your new laptop. Here are a few steps you can try to resolve the problem:

1. Check Java Installation: Although Spine does not use the system-installed Java, ensure that your system is up to date and there are no conflicts with other software.

2. Project Size and Complexity: If your project is large or complex, try exporting a smaller project to see if the issue persists. This can help determine if the problem is related to the project size.

3. Memory Allocation: Increase the memory allocation for Spine. You can do this by running Spine with a command to allocate more memory, such as Spine -Xmx4096m for 4GB.

4. Export Settings: Ensure that your export settings are correct and that you are not using features that might not be supported in your current setup.

5. Reinstall Spine: Try reinstalling Spine 3.8 to ensure that all files are correctly installed and not corrupted.

If the problem continues, it might be helpful to test on another machine or contact Esoteric Software for further assistance.

LuniqueKero Thank you for sending us the Spine project file! Your configuration of cropping and using part of the 12288 * 8192 px image would have caused the export to take so long that I would have thought it was frozen. In fact, even without exporting, just looking at your skeleton in the editor took a long time to load. (By long, I mean only 10-20 seconds, but I can say that the loading time is quite long, since the appearance of a skeleton should generally be seen as soon as the Spine project is opened).

What makes you use such a huge image like this for each attachment? You could just accept long export times, but I think it would be better to modify the skeleton to make it easier to export.