Category: Reliability - Critical Incident ID: X000810 Priority: 9 - Urgent Status: Closed Component: ODMA32.DLL, version 1.5.0 and version 2.0.0
- Repaired in: none required
- Related information:
- Q000600: Troubleshooting WordPerfect-ODMA Integrations
Q000802: Isolating Misbehaving Components
Assigned To: Dennis Hamilton Reported By:
Joseph A. Beeler (2000-08-29)
Date Opened: 2000-08-29 Date Closed: 2000-08-30
A Windows 95 configuration of desktop application, ODMA, and an ODMA-compliant DMS integration demonstrated hogging of resources and a probable memory leak. The condition was isolated to the application program. Repeated operation of the application program then confirmed that the observed problem was not occurring in the ODMA configuration at all. Involvement of ODMA was eliminated, as was involvement of WordPerfect and the PCDOCS DMS.
This incident is closed. The troubleshooting procedures that were employed will be published as a separate ODMA FAQtip for use in similar situations in any ODMA configurations.
On applying the proposed trouble-shooting procedure, it was discovered simply by operating WordPerfect for Windows version 9 in the same configuration both with and without ODMA operation that the undesirable resource drain occurred either way. This eliminated the PCDOCS DMS integration and the ODMA Connection Manager from the problem. There was no difference in behavior as the result of upgrading to the ODMA 2.0 Connection Manager.
Repetitive cycling of WPWin startup, document manipulation, and exit then confirmed that there was no progressive resource drain, again with or without ODMA connection to the DMS.
The testing of an application without ODMA altogether was overlooked in the troubleshooting procedure. Repetitive cycling to confirm that a progressive decline in resources is present was also missing. These checks will be included in the separate FAQtip to be created for all ODMA users to employ when isolating an ODMA component that is suspected of misbehaving.
- 1. WordPerfect for Windows version 9
2. ODMA 1.5 Connection Manager
3. PC Docs' DOCSOpen V3.89.2 Build 41
4. Windows 95 OSR2
- 1. Without opening an application, check the level of system resources
- 2. Run WP9 and do an Open/Save/Close/Exit using the ODMA integration
3. Check system resources again
- 4. The symptom of concern is a dramatic drop in available system resources
This condition is classified as critical because draining of system resources can lead to system crashes and loss of user work.
This is taken on as an ODMA incident until the ODMA Connection Manager is eliminated as a contributor to this problem.
The following steps are recommended for troubleshooting this problem:
- Upgrade the ODMA Connection Manager to the ODMA 2.0 version.
It is recommended that this be done by installing the ODMA 2.0 SDK. This will provide additional test tools and a Connection Manager with special trouble-shooting aids. Backup the ODMA 1.5 Connection Manager before installing the ODMA 2.0 software. See ODMA FAQtip Q000603: Latest ODMA Software.
- Confirm Operation with ODMA 2.0 Connection Manager
There should be no difference in operation, and the application should behave as before. If there is a more-serious failure with introduction of the ODMA 2.0 software, restore the ODMA 1.5 Connection Manager. Immediately report this experience to ODMA Tech.
- Vary Operation to Isolate Resource Hogging.
Taking careful notes so that the problem can be handed over for further analysis by the appropriate development organizations, operate the following variations:
a. First, repeat a test version of the original operation and note whether the resource hogging is still present, and by how much.
b. Second, using the ODMATest application, with DOCSOpen still as the default DMS, perform a similar operation with a simple text document for testing purposes. Notice the before-and-after levels of resource consumption with this case also.
c. Third, remove DOCSOpen as the default DMS by adjusting the Windows Registry so that the
DEFAULTsubkey. Make the ODMA Sample DMS,
ODMASAMPthe default DMS by adding key
d. Repeat the experiment, using WordPerfect to make a document using the ODMA Sample DMS. Note the resource levels before and after.
e. If there is no difference so far, use the ODMA Test application to make a document via the ODMA Sample DMS and see how that leaves the resource levels.
f. Remove the
HKEY_CLASSES_ROOT\ODMA32\ODMASAMP\DEFAULT\Windows registry key and restore the
DEFAULTregistry key for
- Report Your Findings
Provide information on the updating to ODMA 2.0 and on the variations that were performed to determine any pattern in the resource hogging behavior. Report the outcome to ODMA Tech. If the resource hogging occurs only in the presence of a particular application or DMS, provide the same information to the vendor for that component. Provide them with a reference to this incident report also.
created 2000-08-29-10:22 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 00-08-30 17:52 $
$$Revision: 4 $