Board index » Visual Studio » tmp file bloat problem

tmp file bloat problem

Visual Studio267
I've got a COM addin that causes a particular tmp file to bloat every time a

certain procedure is run. The procedure uses several fairly large arrays and

the bloat appears to correspond roughly with what I estimate to be the size

of the arrays that are created during the procedure. It doesn't seem to

matter whether I erase the arrays during the procedure or not, the tmp file

just grows and grows until Word crashes. I can't kill the tmp file because

it's in use - by Word or VB6 I don't know. The tmp file is created when Word

(and the addin) start and is deleted when Word closes properly (causing the

addin to disconnect).



I've posted a question about this in the Word VBA forum, on the chance that

there's something VBA-related that I can do to prevent the bloat, or

eliminate it after it's occurred. I'm posting the question here on the

chance that there's something VB6-specific that I'm doing wrong or that I can

do to solve the problem.



The problem occurs on Win2K/XP and with Word2K/2003, so it seems

platform-independent.



Many thanks for any suggestions/insights etc...


-
 

Re:tmp file bloat problem

Please ignore this thread. I narrowed the problem down and posted a

different question later today. Sorry for any confusion...



"Ken" wrote:



Quote
I've got a COM addin that causes a particular tmp file to bloat every time a

certain procedure is run. The procedure uses several fairly large arrays and

the bloat appears to correspond roughly with what I estimate to be the size

of the arrays that are created during the procedure. It doesn't seem to

matter whether I erase the arrays during the procedure or not, the tmp file

just grows and grows until Word crashes. I can't kill the tmp file because

it's in use - by Word or VB6 I don't know. The tmp file is created when Word

(and the addin) start and is deleted when Word closes properly (causing the

addin to disconnect).



I've posted a question about this in the Word VBA forum, on the chance that

there's something VBA-related that I can do to prevent the bloat, or

eliminate it after it's occurred. I'm posting the question here on the

chance that there's something VB6-specific that I'm doing wrong or that I can

do to solve the problem.



The problem occurs on Win2K/XP and with Word2K/2003, so it seems

platform-independent.



Many thanks for any suggestions/insights etc...

-