rejetto forum
Software => HFS ~ HTTP File Server => Bug reports => Topic started by: Giant Eagle on November 01, 2007, 03:26:46 PM
-
Access violation at address 004056F7 in module 'hfs.exe'. Read of address 52542F38
HFS 2.2a
----------------------------------------------------------------
Stack list, generated 1-11-2007 16:21:27
(000046F7){hfs.exe } [004056F7]
(0011A292){hfs.exe } [0051B292]
(00001D68){hfs.exe } [00402D68]
(00004315){hfs.exe } [00405315]
(00124F81){hfs.exe } [00525F81]
(001260D9){hfs.exe } [005270D9]
(00127BA5){hfs.exe } [00528BA5]
(0012D8A9){hfs.exe } [0052E8A9]
(0012E26E){hfs.exe } [0052F26E]
(000A921D){hfs.exe } [004AA21D]
(000AB33C){hfs.exe } [004AC33C]
(000AA7F4){hfs.exe } [004AB7F4]
(000A901A){hfs.exe } [004AA01A]
(000A91C0){hfs.exe } [004AA1C0]
(0004E57F){hfs.exe } [0044F57F]
(0004E3EB){hfs.exe } [0044F3EB]
(000293FC){hfs.exe } [0042A3FC]
(00075208){hfs.exe } [00476208]
(0006C70E){hfs.exe } [0046D70E]
(0006C753){hfs.exe } [0046D753]
(0006C9EE){hfs.exe } [0046D9EE]
(0014A5AB){hfs.exe } [0054B5AB]
----------------------------------------------------------------
System : Windows XP Professional, Version: 5.1, Build: A28, "Service Pack 2"
Processor: Intel, Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz, 2400 MHz MMX
Display : 1680x1050 pixels, 32 bpp
----------------------------------------------------------------
----------------------------------------------------------------
Product Versions
hfs.exe: Build: 0 28-9-2007 21:29:02
hfs.old.exe: Build: 0 20-9-2007 19:17:16
Here's what i did:
- Tried to browse a folder which i couldnt open, 'Slow response' bug i think. HFS said: "Replying", after a minute i stopped the request
- Started streaming a music file in the folder i was currently browseing
- At that moment, HFS was searching for an update
Then the error came up. Could be cooincidence tho
-
build 137 i guess, right?
-
No I Think Its.... Build 124....... ?
-
next builds will report the build number
too bad i didn't do it before
-
2.2a build 124 is or 137 its 100% working ... i think its not hfs error. its windows error. not sure... may b registry error.... wht u think ?
-
build 137 i guess, right?
Yes, sorry for not mentioning.
-
had a look at that address but found nothing :(