OLE Automation Problems - MEMORY HOG (Memory Leak?)

OLE Automation Problems - MEMORY HOG (Memory Leak?)

Post by <r.. » Sat, 01 Jul 1995 04:00:00

I'm developing an application which uses VB for OLE Automation to MS Word 6.0c.
I'm pulling bookmark information from a document so that my application can
"follow along" as the user moves through a context-tagged Word document,
providing over-the-shoulder advice for modifying document content based on

I build an array of the bookmarks in the document, and periodically (every half
second at this point) do a cmpBookmark with OLE to see which bookmark(s) the
cursor is located in.  No problem there.  The problem is that, depending on how
much RAM is in the system on which it's running, I eventually (5-10 min. max.) get
an "OLE Automation Error - Out of Memory" from VB.  It terminates, and leaves me
with a Word dialog saying "Out of Memory - save your file and exit Word."

I've tried moving the wdBasic method call into a separate procedure, to ensure
object is released each time.  I've tried reducing the number of bookmarks to
free resources.  (In development, I was using about a dozen.  Live data has 95,
and for testing purposes, I trimmed that down to about 55, and the problem

Does anybody know of any memory leaks in Word's OLE automation, or problems
with OLE automation that would cause this, preferably problems that have

Help would be appreciated; please copy me by e-mail if possible, since I only get
into the newsgroups every couple days.

Rick Rutledge


1. Memory Leak with Ole Automation in SQL Server when using seagate crystal reports

daily Iam printing seagate crystal reports using ole automation functions of
sql server. This sql server is our backup server. Once in a week i have to
reboot this server since every day the memory usage increases. There are no
major applications which are running on the backup sql server.

Please help me with any pointers or info or suggestions.


2. Bit-Mapped Indexing Routines---Beta Testers Wanted

3. Memory Leak When You Use SQL Server When I use OLE Automation Stored Procedures

4. unused index

5. SQL Server hogging up CPU usage / memory leaks

6. Clustering and Constraints in a table

7. SQL Server seems to leak memory until complete out of memory

8. locking

9. memory leak on vitual memory

10. Memory Leak - Running out of Virtual Memory

11. memory leak in vitual memory

12. SQL Server OLE DB memory leaks