Shutdown error in FC_2009.02 - very frequent
Posted: 22.07.2009, 07:21
My first post here. I have almost exclusively been using FC for the last 2 years as my file manager and have noticed a lot of things, both bugs and things to add to my wish list.
I figure I'd start with a very persistant and annoying bug that happens when closing the FC window (using the X in the upper right-hand corner).
I get this error messaage in a Windows message error box with the red "X"(sorry, It wouldn't let me paste a 7k jpg file here)...
---------------------------------------------------------------------------------
"The instruction at "0x01735d75" referenced memory at "0x00000008".
The memory could not be "read".
Click OK to terminate the program
----------------------------------------------------------------------------------
This error occurs regardless of which of the 3 computers I have it installed on. The only consistancy between the 3 PC's is that they are all running different flavors of Windows XP SP3 (WinXP Pro, WinXP Home, WinMCE2005). All have different CPU's and graphics cards.
So its not a physical memory error like I first thought. It usually only happens when FC has been up at least 30 mins, and has little to do with whether I've performed a lot of tasks with it or not).
The bolded memory reference above is always the same. (0x0...
.
I hope this is somewhat helpful in debugging.
And thanks for writing a great tool that I use frequently,
Wulffie.
I figure I'd start with a very persistant and annoying bug that happens when closing the FC window (using the X in the upper right-hand corner).
I get this error messaage in a Windows message error box with the red "X"(sorry, It wouldn't let me paste a 7k jpg file here)...
---------------------------------------------------------------------------------
"The instruction at "0x01735d75" referenced memory at "0x00000008".
The memory could not be "read".
Click OK to terminate the program
----------------------------------------------------------------------------------
This error occurs regardless of which of the 3 computers I have it installed on. The only consistancy between the 3 PC's is that they are all running different flavors of Windows XP SP3 (WinXP Pro, WinXP Home, WinMCE2005). All have different CPU's and graphics cards.
So its not a physical memory error like I first thought. It usually only happens when FC has been up at least 30 mins, and has little to do with whether I've performed a lot of tasks with it or not).
The bolded memory reference above is always the same. (0x0...
.I hope this is somewhat helpful in debugging.
And thanks for writing a great tool that I use frequently,
Wulffie.