After fixing several parallelism errors, no memory errors have been detected at all with `valgrind`, in `QBdt`. (Depending on one's system, a couple of string comparison memory errors might be present on program initialization, not rooted in Qrack user code, but this is all the developers currently detect with `valgrind`.)
We still recommend, depending on simulation method, that simulations with _maximum separable subsystem footprints_ larger than 32 qubits use at least `double` build precision, and footprints larger than 64 qubits should use `quad`. (PyQrack on PyPi only provides a 32-bit `float` build, but build from source, to tailor for your needs.)