BUG in .NET 1.1 HOW TO FIX "Hashtable insert failed. Load factor too high" ??

  • Thread starter Thread starter Sazonov Dmitry
  • Start date Start date
S

Sazonov Dmitry

I got exeption in production environment:

A first chance exception of
type 'System.InvalidOperationException' occurred in
mscorlib.dll

Additional information: Hashtable insert failed. Load
factor too high

Also I found article
http://support.microsoft.com/Default.aspx?kbid=831730

But it does not say where can I download fix for this
bug. It just forwarded me to "support center" where they
want to charge me $250/hour for fixing they own bugs.

We are loosing money because of this bug.

Please help to fix it A.S.A.P.
 
If you contact support and it is determined that this is your error, you will
not be charged for the call. The charge will only be assessed if the
mentioned bug fix is not your issue.

There may be a way to alleviate the problem.

1. How big is the Hashtable you are loading (ie, how many records)?
AND, more importantly
2. How much memory is the Hashtable consuming?

If you are loading HUGE Hastables, you will overrun the 2 GB limit per
process. This should throw an out of memory exception, but I am not sure this
is 100%. If you think this might help, there are two potential solutions to
this issue:

1. Move your application to a 64-bit machine, which has a much larger
address size. Have not tested this, but it has been suggested.

2. Increase the amount of memory per process in the registry. NOTE: If you
go this route, make sure you do not lift the value so high that you go over
your machine memory limit (factor in overhead for OS and all services
running, as well).

If these suggestions offer no solice, I would consider calling MS support.
If it turns out to be MS's fault (you found a bug, either the one mentioned
or a new one), you will not be charged.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
My hashlable is pretty small, around 2000 elements.
Referenct-to-support class (which contains 2 double)
I guess payload of this hashtable should be (4+8*2)*2000
= 40Kb.

I'm creating 130 such hashtables. So, total memory should
not exceed 5-10MB

My total memory usage for applicaiton is about 100MB.
Machine has 2GB RAM and no other working processes.

this problem is not related to huge memory usage. It is
microsoft's bug.

I was able to fix it (I hope) by pre-creating my
hashtable before usage. Also, I called to microsoft and
got hotfix for that.

thanks.
 
Sazonov Dmitry said:
My hashlable is pretty small, around 2000 elements.
Referenct-to-support class (which contains 2 double)
I guess payload of this hashtable should be (4+8*2)*2000
= 40Kb.

I'm creating 130 such hashtables. So, total memory should
not exceed 5-10MB

My total memory usage for applicaiton is about 100MB.
Machine has 2GB RAM and no other working processes.

this problem is not related to huge memory usage. It is
microsoft's bug.

I was able to fix it (I hope) by pre-creating my
hashtable before usage. Also, I called to microsoft and
got hotfix for that.

thanks.
Click to expand...

If you had installed SP1 for the v1.1 framework you wouldn't have had this
problem, this bug was fixed before SP1.

Willy.
 
Back
Top