Click here to get back home

Large Index crashes machine (memory leak, handle leak?)

 HomeNewsGroups | Search | About
 microsoft.public.msn.search    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
Large Index crashes machine (memory leak, handle leak?) MatthiasGƭgbˬ*'h( 05-25-2005
Posted by MatthiasGƭgbˬ*'h( on May 25, 2005, 4:33 am
Please log in for more thread options


I have a machine with about 1 million items to search across on about 600 GB
harddrive space. The bug below was also apparent in the beta version and
shows up on several of our machines with enough files.

When i let the index build itself, after a couple of hours the index nears
completion (no new items left to index appear), the system becomes unstable.
The effect is, that the desktop or logon pages first dont show any icons
anymore and then window borders are also lost.

After restarting the system, desktop search show index complete, but it wont
find anything anymore and tells me that 0 items have been indexed and none
are left to index. Rebuilding fixes the problem as long as the index is being
built and then runs into the problems mentioned above...

Looks like a memory leak or handle leak to us


Posted by Brandon Paddockڝ'=]. on May 25, 2005, 10:13 am
Please log in for more thread options


Is it possible you're running into one of the following problems?

http://support.microsoft.com/default.aspx?scid=kb;en-us;126962

http://support.microsoft.com/default.aspx?scid=kb;en-us;327699

"MatthiasG" wrote:

> I have a machine with about 1 million items to search across on about 600 GB
> harddrive space. The bug below was also apparent in the beta version and
> shows up on several of our machines with enough files.
>
> When i let the index build itself, after a couple of hours the index nears
> completion (no new items left to index appear), the system becomes unstable.
> The effect is, that the desktop or logon pages first dont show any icons
> anymore and then window borders are also lost.
>
> After restarting the system, desktop search show index complete, but it wont
> find anything anymore and tells me that 0 items have been indexed and none
> are left to index. Rebuilding fixes the problem as long as the index is being
> built and then runs into the problems mentioned above...
>
> Looks like a memory leak or handle leak to us


Similar ThreadsPosted
Indexing large xml files March 10, 2006, 10:41 am
Desktop search bar too large April 28, 2007, 11:03 am
WDS not fully indexing large text files March 26, 2006, 5:53 pm
how come I can't search for machine.config with msn desktop search? August 5, 2005, 2:58 pm
memory could not be read October 16, 2005, 5:46 am
The memory could not be "read". October 7, 2005, 12:33 am
desktop search memory footprint May 16, 2005, 5:31 pm
Tabbed Browsing and excessive memory usage December 14, 2005, 11:33 am
Acrobat Reader Process Stays in Memory April 3, 2006, 3:47 pm
WDS 2.06.5 Crashes and I think I am onto something March 12, 2006, 7:25 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap