An application uses up more and more memory, until all swap space is exhausted.
Third-party software can help identify memory leaks in their applications. If you suspect that you have a memory leak, you can use sar(1) to check on the Kernel Memory Allocation (KMA). Any driver or module that uses KMA resources, but does not specifically return the resources before it exits, can create a memory leak.
For more information on memory leaks, see the section on monitoring system activity in the System Administration Guide, Volume 2. If you are using AnswerBook online documentation, "displaying disk usage" is a good search string. Also, see the section on system resource problems in the NIS+ and FNS Administration Guide.