Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Users may report an error message in LawMaster due to the OOM.


When it comes to determining the cause for an OOM condition, you are actually working to determine the cause for either a high memory situation or a fragmented address space. While there is no way to document all of the possible causes of these situations, there are some common causes that we see regularly.

  • Returning Large Sets of Data
    When retrieving data from LawMaster, it’s important to limit the amount of data returned using the Max Records for example.  Trying to return all folios when the max records is set at 10000 for example is a common way to create a high memory situation.
  • SQL Server with Pending Updates
    We have noticed that a Pending update and server waiting to reboot can caused the OOM error to appear


  • Returning Large Sets of Data
    Always limit the amount of data that can be returned from a database. If you have set the max records to 10000 or a similar large value, try to reduce the number to a lesser value or use advanced filter to narrow down your query results.
  • Restart LawMaster Application Service:
    We have seen the Application Service use more memory when someone does a particularly large query. However, this matter doesn't seem to be always an issue. But would certainly be affected if someone did a large query.
    Usually these have been tracked most of the times to the UDQ's that users have run. If you are able to find out what everyone was running about the time the issue appeared, it would be helpful in locating the issue.
    Stopping and re-starting the LawMaster Application Service that is using the memory would normally being everything back to normal operation again. Although it does still kick everyone off.

  • SQL Server with Pending Updates:
    Reboot the server and keep the server upto date with all the critical server updates recommendation from Microsoft.


If this is a error that is reoccurring at your firm and if you are hosting your own database, we would request you to enable windows logs to capture memory utilization on the server and PC in question when consumption exceeds 90% or more as the logs will help is ascertaining the memory intensive application and further evaluation.