Previous Page: Ensuring That Devices Can Access Memory  Next Page: Tuning Server Memory

Determining Which Processes Use Too Much Memory

To determine which NLM programs are using excessive amounts of memory (have a memory leak), complete the following steps.

NOTE:  Complete Step 1 in either NetWare Remote Manager or MONITOR.

  1. Watch the memory usage trends for any NLM that you might suspect has a problem. Any NLM that has a memory pool that is constantly growing might have a memory leak.

  2. Watch for "Short term memory allocator is out of memory" alerts displayed at the System Console or Logger screen or in the system log files. Often one NLM stands out with an unusually large memory pool.

In NetWare Remote Monitor

  1. Click the List Modules link in the navigation frame.

  2. Sort the list by allocated memory usage by clicking the Alloc Memory button in the table.

    NOTE:  SERVER.NLM and NSS.NLM will always be high memory users.

  3. View the Allocation Summary page for each NLM that is listed at the top of the list by clicking the Alloc Memory value link for each NLM.


  1. From the Available Options menu, select Loaded Modules.

  2. Select a module from the list to display its information and statistics in the upper window.

  3. Press Tab to expand and activate the Module Information window.

  4. Check the module's Allocated Memory.

    The information includes bytes of memory required to load, allocated memory bytes in use, percent of memory in use, allocated memory bytes free, percent of memory free, and the module's load flags. Press F1 for a description of these statistics.

  5. Press Tab to return to the list of loaded modules.

  6. Check the memory statistics for other modules.

  7. (Optional) Press F4 to free memory allocated for a selected module.

If you suspect an NLM program has a memory leak, you can unload and reload the NLM to solve the problem temporarily. To solve the problem permanently, contact the vendor of the program and request them to fix the program.

  Previous Page: Ensuring That Devices Can Access Memory  Next Page: Tuning Server Memory