Sean Fitzpatrick

On Windows the OOM errors are fixed. I can do offscreen rendering of 3D images to PDF successfully. There might be some work to do on the PreTeXt side: on an old Linux laptop with 16 GB RAM, our build script runs through all 300+ images with no problem. On a newer Windows laptop with twice the memory, generation fails after about 200 images, and it seems to be a memory issue again (I can build any subset of 150 images just fine). Anyway perhaps one should not use Windows for heavy lifting.

I tested a bit before the official release (built from Git source) and I now get a clean run building all 300+ Asymptote figures in APEX Calculus. This is on Linux. I'll test Windows later, and once I can get the attention of the person who maintains the PreTeXt devcontainer, I'll test there as well. Thanks for the quick fix for the memory issue!

Great! I will try to test the new version soon.

I've hit an error that also occurs on the U of A server, so it's not just my installation. I tried to start a new thread for this, but it went to "waiting for moderation" 5 days ago and never appeared. The error is g=tex ? _texpath(s,p) : textpath(s,p); ^ /usr/local/share/asymptote/plain_Label.asy: 664.6: runtime: Cannot fork process I've attached the .asy file for which the error occurs. This image compiles fine to both html and pdf with Asymptote 2.87. I was able to build HTML on my laptop, but...

John: some reporting on a bit of trial and error on various platforms. Things build fine on the U of A server. (No surprise there) With 3.12 on Windows, quite a few of our 3D images are hitting OOM errors with over 20GB of memory available With 3.09 on Windows (via TeXLive 2026), I can't build PDF at all (maybe I need the right parameters). I get the following error: freeglut (asy): fgPlatformInitialize: CreateDC failed, Screen size info may be incorrect This is quite likely caused by a bad '-display'...

Oh, thanks! I'll send this to the person who maintains the Docker image. We also use devcontainers, so it should just be a question of compatibility. (I hope! I'm just the middle-man between the person who maintains the Docker stuff and a person who wants to use it.)

OK, there is something wrong with how asy 3.12 was built in the docker container. I got it working locally and the image looks correct.

I should clarify that the HTML build was done locally using 2.87. If I build HTML in codespaces with 3.12 and the same source file, I get the same image as the pdf.