MetaSolv Solution tbs.exe Client Crashes with "Out of Memory" Error after Working Numerous EWO Orders

(Doc ID 2209911.1)

Last updated on FEBRUARY 22, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Symptoms

Users receive an "Out of Memory" error from their MetaSolv Solution tbs.exe client and it crashes.  Users reports the error occurs several times per day while performing normal activities of completing out tasks, updating EWOs with data and saving and continuing. Users also report the problem occurs after working around 20 to 30 EWO orders.  The Windows Task Manager shows the memory utilization of the tbs.exe process at 1,314,580K (1.3 GB) when the client crashes.


Error text

1. Open the Windows Task Manager

2. Open the MetaSolv Solution client (tbs.exe) <-- Note the memory utilization of the process (~46 MB)

3. Order Management

4. Click Add New

5. Select Engineering Work Order and click OK <-- Note the memory utilization of the process (~330 MB)

6. Enter the required fields and click Save and Continue <-- Note the memory utilization of the process (~173 MB)

7. Close the EWO order <-- Note the memory utilization of the process (~156 MB)

8. Query for the newly added EWO <-- Note the memory utilization of the process remains the same

9. Open the EWO <-- Note the memory utilization of the process only increases slightly (~158 MB)

10. Click Edit to change the Work Order Information <-- Note the memory utilization of the process increases sharply (~394 MB)

11. Click Save and Continue <-- Note the memory utilization of the process decreases (~248 MB), but not to the level at step 6

12. Close the EWO <-- Note the memory utilization of the process decreases (~233 MB), but not to the level at step 7

13. Open the EWO <-- Note the memory utilization of the process only increases slightly (~236 MB)

14. Click Edit to change the Work Order Information <-- Note the memory utilization of the process increases sharply (~460 MB)

15. Click Save and Continue <-- Note the memory utilization of the process decreases (~321 MB), but not to the level at step 6 or 11.



Business Impact

Due to this issue, the user must close the application and re-login.

 

Changes

Implementation of EWO User Data amplified by a drop-down field having a significant number of values to choose.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms