Unhandled Exception - on Windows XP

[pr0wler]

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

InvalidArgument=Value of '0' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.




************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '0' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex
at System.Windows.Forms.ComboBox.set_SelectedIndex(In t32 value)
at HoldemManager.PlayerSummary..ctor()
at HoldemManager.frmMain3.h()
at HoldemManager.frmMain3..ctor(frmLoading LoadingForm)
at HoldemManager.frmLoading.a(Object A_0, EventArgs A_1)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndPr oc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
HoldemManager
Assembly Version: 1.10.0.5
Win32 Version: 1.10.0.5
CodeBase: file:///C:/Program%20Files/RVG%20Software/Holdem%20Manager/HoldemManager.exe
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
DevComponents.DotNetBar2
Assembly Version: 8.3.0.0
Win32 Version: 8.3.0.0
CodeBase: file:///C:/Program%20Files/RVG%20Software/Holdem%20Manager/DevComponents.DotNetBar2.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

etc.......

I've read some of the other threads regarding this issue. I have SP3 2002, updated the MS framework and uninstalled using the Revo Uninstall software. Reinstalled and updated to 1.10.04b. Not using any anti-virus software either, disabled windows firewall and I even put up an exception for Holdem Manager...still no luck. Are there any confirmed solutions to this problem?

[netsrak]

You are trying to select a player name in the reports?

Please click directly on the change button not on the arrow besides.

In the upcoming window enter the first characters of a player name.

[AKQJ10]

Has this been reported as a bug? The HEM app should really not be exposing a way for the user to make it blow chunks. :)

Probably would be triaged as medium-priority, since there is a good workaround.

[LotteryGuy]

This error occurs when HEM is pre-fetching user names when you type letters of the player name. I think it is some kind of synchronization issue with the thread that fetches possible usernames from database and the thread that reads user input from the box.

Maybe the problem is that user enters 3 letters, makes a slight pause, HEM starts the DB query for nicknames, user enters one more letter and HEM starts another DB query while the first one is still running?

Maybe the previous DB thread is partly destroyed when launching a new thread and therefore the reference to the old DB thread triggers this error condition.

Just pure speculation on the origin of the problem...