Discussion:
Memory error calling CommitUrlCacheEntry
(too old to reply)
Brad Wood
2004-04-16 18:12:34 UTC
Permalink
On certain user's machines, I get system error #8 ERROR_NOT_ENOUGH_MEMORY
upon calling CommitUrlCacheEntry (I have definetely narrowed it down to this
call).
When I test overloading the internet cache on any machines in house, I never
see an error (I set the designated amount of cache space to only 1MB).
Whe a user of an affected machine clears his Internet cache via Internet
Options, everything works OK. This is confusing to me because the error is
memory related, but clearing up disk space fixes it.

I'm just hoping somebody has some suggestions as to what might be causing
this.
Stephen Sulzer
2004-04-16 21:22:12 UTC
Permalink
ERROR_NOT_ENOUGH_MEMORY from CommitUrlCacheEntry likely indicates that the
IE cache database table is full. (The IE cache database table is stored in
the index.dat file.) Regardless of how much disk space is allocated for the
IE cache, it can only store a fixed number of entries (files, cookies,
etc.). I'm not sure what the limit is.

This cache entry limit will very likely be encountered on systems that have
allocated a lot of disk space (hundreds of megabytes or more) for the IE
cache, rather than on your system with only 1MB reserved. So clearing the
cache clears the database table and resolves the problem. You can test the
limit by setting the IE cache very large (say 100MB) and then repeatedly add
small files (say, 500 bytes each) until CommitUrlCacheEntry returns the
memory error.

Stephen
Post by Brad Wood
On certain user's machines, I get system error #8 ERROR_NOT_ENOUGH_MEMORY
upon calling CommitUrlCacheEntry (I have definetely narrowed it down to this
call).
When I test overloading the internet cache on any machines in house, I never
see an error (I set the designated amount of cache space to only 1MB).
Whe a user of an affected machine clears his Internet cache via Internet
Options, everything works OK. This is confusing to me because the error is
memory related, but clearing up disk space fixes it.
I'm just hoping somebody has some suggestions as to what might be causing
this.
Loading...