- Trending Categories
- Data Structure
- Operating System
- MS Excel
- C Programming
- Social Studies
- Fashion Studies
- Legal Studies
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
How to avoid memory leakage in SAP B1 DI API
The thumb rule goes like this, if you instantiate a DI API object, you have to release it. if you don't release it explicitly, it will result in memory leaks.
You can use a ReleaseComObject method to release the object memory. In case if you try to release a null object, it will throw an exception.
So, it will be better to have a null check before you try to release the object.
if (obj != null) System.Runtime.InteropServices.Marshal.ReleaseComObject(obj);
- Related Articles
- Connecting SAP B1 via DI API takes too much time
- Difference between SBObob GetItemPrice and CompanyService GetItemPrice in SAP B1?
- How to use EXPORT / IMPORT to Memory ABAP – SAP?
- Using memory analyzer in SAP
- In-memory read in SAP HANA
- SAP SuccessFactor OData API access
- DI String Match in Python
- EI and DI instructions in 8085
- Getting memory error while doing UNION in SAP HANA
- Increasing memory of traditional database as compared to SAP HANA
- Updating Data source of provider by REST API in SAP
- Valid Permutations for DI Sequence in C++
- Checking monthly main memory utilization peak values in SAP HANA
- How to avoid “StaleElementReferenceException” in Selenium?