Logic may quit unexpectedly on systems with large amounts of RAM

Resolution

This issue may appear to be related to using Logic on systems with large amounts of physical RAM, but the actual cause is likely something else. One possible cause is the amount of Virtual Memory used by Logic when the situation arises. Logic may quit unexpectedly when its Virtual Memory footprint approaches 4 GB. The best practice is to keep Logic's Virtual Memory use to less than 3.5 GB. You can monitor Virtual Memory use with the Activity Monitor application, which is at /Applications/Utilities on the startup drive.

One of the more common reasons that a project may require a large Virtual Memory footprint is extensive use of samples. If you are using the EXS24, a possible work around is to enable Virtual Memory for the EXS24. This should not be confused with Virtual Memory at the system level. Enabling Virtual Memory for the EXS24 causes it to stream samples directly from the disk, lowering the amount of RAM required to play them, and thus making it less likely that Logic will require a large amount of system Virtual Memory. To enable Virtual Memory for the EXS24, choose Options > Virtual Memory in the upper right area of the EXS24 plug-in window. If you use other sampler plug-ins, consult their documentation to see about enabling disk streaming.

The Pro Application Support 4.0 update may enhance Logic's stability with large projects. You can get Pro Application Support 4.0 via Software Update or by clicking here.