Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
We recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once.
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
Error 10 (0000000A)
Desc This array is fixed or temporarily locked
Dll 0
Proc
Source XYplorer
XY ver 9.10.0000
OS Windows Vista (Service Pack 2)
Date 06/05/2010 16:53:35
Used to update to the latest beta every day. Now I have children instead… Windows 10 Pro x64 (everywhere except phone…)
Error 10 (0000000A)
Desc This array is fixed or temporarily locked
Dll 0
Proc
Source XYplorer
XY ver 9.10.0000
OS Windows Vista (Service Pack 2)
Date 06/05/2010 17:01:48
Used to update to the latest beta every day. Now I have children instead… Windows 10 Pro x64 (everywhere except phone…)
I've seen this once today on Windows 7 x64 with 9.10.0000. I didn't log the bug data, but looks identical at first sight (error 10). On pressing Enter after inline rename, XYplorer.exe's CPU usage skyrockets. After a few attempts to close XYplorer regularly, it crashes.
admin wrote:Only I cannot reproduce it on XP. How exactly are you renaming/deleting?
I selected a file (.wmv, if that matters) in the List which was set to List view, pressed F2 to rename inline, edited the file name and pressed Enter. I can't reproduce it currently.
admin wrote:Only I cannot reproduce it on XP. How exactly are you renaming/deleting?
I selected a file (.wmv, if that matters) in the List which was set to List view, pressed F2 to rename inline, edited the file name and pressed Enter. I can't reproduce it currently.
Frightening. Hard to debug. Argh. Looks like it's time to finally get me that virtual box..
admin wrote:Frightening. Hard to debug. Argh. Looks like it's time to finally get me that virtual box..
I'll keep a lookout for more occurrences, but a not reliably reproducible problem is awkward. I believe this thread had some info regarding VirtualBox.
In case it's relevant: I have deletes backgrounded. At the risk of making myself look ridiculous: could that array mentioned in the OP's bug report have anything to do with the background jobs list?
OTOH, renames are not backgrounded, so... (I did mention ridiculous, didn't I? )
Interestingly, I noticed several (5 I think) XYcopy.exe instances running in programme manager when I went to check if XY was still "running" after it crashed. I killed them all and then restarted.
This bug occurs intermittently for me on renaming, both F2 and slow double click, but it also happens on moves, deletes and copies (all of these done via CTRL+X/C/V). After a crash/restart it either starts up again almost immediately, or not for hours.
I've not noticed this on my Win7 x64 bx, but I don't run that so hard on the file management. I've only seen this so far on Vista SP2 x64.
You're still using WindowsXP? Frankly, the massively improved windows organisation and management features in Windows 7 is reason enough to upgrade (Win+ArrowKeys).
P.S. installing stuff into Vbox is completely straightforward now, you should be able to do it in your sleep. Just make sure you install the "Additions", by default, press Right CTRL+D once the guest OS is installed.
Used to update to the latest beta every day. Now I have children instead… Windows 10 Pro x64 (everywhere except phone…)
lukescammell wrote:Interestingly, I noticed several (5 I think) XYcopy.exe instances running in programme manager when I went to check if XY was still "running" after it crashed. I killed them all and then restarted.
This bug occurs intermittently for me on renaming, both F2 and slow double click, but it also happens on moves, deletes and copies (all of these done via CTRL+X/C/V). After a crash/restart it either starts up again almost immediately, or not for hours.
When XY goes down crashing, it cannot close any XYcopy.exe.
You also get crashes when you do not use background processing (and no XYcopy.exe is hanging in memory)?
>>After a crash/restart it either starts up again almost immediately, or not for hours.
What do you mean by this?
Just got a slightly different variant of this crash - it just gave me an "Error 10" popup with an OK button. Clicking the OK button crashed XY out. I was attempting to rename a directory. I've been running with auto-refresh off. I think I''ll stick it back on since it doesn't seem to make a difference.
I'll try running without any background tasks.
I meant that either I get another crash almost straight away, or it works fine again for several hours before crashing.
Regarding the multiple XYcopy.exe's in memory. Wouldn't it make sense to do a check for them on XYplorer.exe startup? If there are no other XYplorer.exe's running it would make sense to close the XYcopy.exe processes just to keep things tidy.
Used to update to the latest beta every day. Now I have children instead… Windows 10 Pro x64 (everywhere except phone…)
lukescammell wrote:Just got a slightly different variant of this crash - it just gave me an "Error 10" popup with an OK button. Clicking the OK button crashed XY out. I was attempting to rename a directory. I've been running with auto-refresh off. I think I''ll stick it back on since it doesn't seem to make a difference.
I'll try running without any background tasks.
I meant that either I get another crash almost straight away, or it works fine again for several hours before crashing.
Regarding the multiple XYcopy.exe's in memory. Wouldn't it make sense to do a check for them on XYplorer.exe startup? If there are no other XYplorer.exe's running it would make sense to close the XYcopy.exe processes just to keep things tidy.
I think about a self-destructing mechanism for idle XYcopy.exes.
Tomorrow I go shopping. Hardware + win7 (+ vbox). The time has come.