Closed GoogleCodeExporter closed 8 years ago
It's a bit bizarre to be honest. The crash is in the dnspython library, which
is unable to
read your registry for some reason. Somewhere there is a ü character. I'll put
in a
workaround so that if it cannot read the registry, that it doesn't crash.
Original comment by tstromb...@google.com
on 8 Dec 2009 at 12:17
Workaround committed in revision 414. Will be part of 1.0.1 release.
Original comment by tstromb...@google.com
on 8 Dec 2009 at 12:39
1.0.1 has been posted - can you confirm if this fixes the bug, or simply moves
the
crash around?
Original comment by tstromb...@google.com
on 8 Dec 2009 at 2:00
I do not get the same error now. However it still does not work.
The unzip progress bar goes to the end and then freezes. It says "Unzipping...
(Not
Responding)". Then the namebench menu comes up and when I click on "Start
Benchmark"
I see a pop up that says:
list index out of range
File"libnamebench\nameserver_list.pyc", Line 123, in_init_
File"libnamebench\nameserver_list.pyc",line 209, in
ApplyCongestionFactor
File"libnamebench\conn_quality.pyc",line 50, in
CheckConnectionQuality
File"libnamebench\conn_quality.pyc",line 44, in
GetNegativeResponseDuration
Original comment by alexwie...@gmail.com
on 8 Dec 2009 at 2:42
Attachments:
Also when I close out of the program I get this error
"See the Logfile at C:\Users\Alex\AppData\Local\Temp\ckz_6SPR\namebench.exe.log"
This is what the file says:
Traceback (most recent call last):
File "libnamebench\tk.pyc", line 85, in run
File "libnamebench\base_ui.pyc", line 58, in PrepareBenchmark
File "libnamebench\nameserver_list.pyc", line 123, in __init__
File "libnamebench\nameserver_list.pyc", line 209, in ApplyCongestionFactor
File "libnamebench\conn_quality.pyc", line 50, in CheckConnectionQuality
File "libnamebench\conn_quality.pyc", line 44, in GetNegativeResponseDuration
IndexError: list index out of range
Original comment by alexwie...@gmail.com
on 8 Dec 2009 at 2:45
This should be fixed in version 1.0.2.
Original comment by tstromb...@google.com
on 8 Dec 2009 at 7:35
Everything appears to be working now. Thanks for the fixes.
Original comment by alexwie...@gmail.com
on 9 Dec 2009 at 2:35
Original issue reported on code.google.com by
alexwie...@gmail.com
on 7 Dec 2009 at 11:51