CRASH: WOW64 Redirect on Vista 64

[Jeff Bellune]

OS: Vista 64 SP1
XYplorer version: 7.90.0050 release

Problem description:
With WOW64 Redirection unchecked in the View menu, XY crashes when another tab is selected with the mouse.

Steps to reproduce:
1. Open an instance of XY
2. Go to View | Show Items and uncheck WOW64 Redirection (64-bit only)
3. Click on a different tab than the current tab.

Results:
XY crashes with the following error message:
Run-time error '97':
Can not call friend function on object which is not an instance of defining class

Cannot close the error message, nor XY. XY must be force quit via Task Manager.

Expected Results:
No crash with WOW64 Redirection unchecked. This was the case in earlier versions of XY.

-Jeff

[admin]

If you do a restart after unchecking WOW64 Redirection, you still crash?

[Jeff Bellune]

If you do a restart after unchecking WOW64 Redirection, you still crash?

If I restart XY, I still get the crash. I did not test restarting the computer.

-Jeff

[noir]

Just tested this in windows 7 beta 64bit, with XY 7.90.0050 and i didn't get any crashes.
so its either a isolated case , a vista issue or could also depend on view or other settings, i had mine on details view

maybe you need to update your 32/64 c++ runtimes.

you can probably check this by looking in your system eventlog and seeing if there is any side by side errors.

[admin]

If you do a restart after unchecking WOW64 Redirection, you still crash?

If I restart XY, I still get the crash. I did not test restarting the computer.

-Jeff

Are you previewing anything (preview panel) when changing the tab?

[Jeff Bellune]

Update:

Initial Conditions:

1. Mini-Tree is loaded on XY start.
2. Top-level "Computer" folder is displayed in the List pane.
3. All drives are shown in the List pane, but only some of the drives are shown in the mini-tree.
4. If the very first operation performed in a new instance of XY is to uncheck View | Show Items | WOW64 File Redirection, then I get the crash as described above when a tab is clicked. If a catalog item or a tree node is clicked, then I get an error 48/File not found message.

Workaround:

1. Visit any tab, any tree node or any catalog item *before* unchecking WOW64 File Redirection. This will prevent the crash.

Hope this helps, Don. Let me know if you want any of my configuration/settings files.

-Jeff

[admin]

Update:

Initial Conditions:

1. Mini-Tree is loaded on XY start.
2. Top-level "Computer" folder is displayed in the List pane.
3. All drives are shown in the List pane, but only some of the drives are shown in the mini-tree.
4. If the very first operation performed in a new instance of XY is to uncheck View | Show Items | WOW64 File Redirection, then I get the crash as described above when a tab is clicked. If a catalog item or a tree node is clicked, then I get an error 48/File not found message.

Workaround:

1. Visit any tab, any tree node or any catalog item *before* unchecking WOW64 File Redirection. This will prevent the crash.

Hope this helps, Don. Let me know if you want any of my configuration/settings files.

-Jeff

Okay, my theory is that starting up on "MyComputer" is the crucial point. Can you, or anybody else, confirm this? I assume, XY attempts to load a 64-bit module when the first file browsing happens after WOW64 redirection is disabled.

[Jeff Bellune]

Update:

Initial Conditions:

1. Mini-Tree is loaded on XY start.
2. Top-level "Computer" folder is displayed in the List pane.
3. All drives are shown in the List pane, but only some of the drives are shown in the mini-tree.
4. If the very first operation performed in a new instance of XY is to uncheck View | Show Items | WOW64 File Redirection, then I get the crash as described above when a tab is clicked. If a catalog item or a tree node is clicked, then I get an error 48/File not found message.

Workaround:

1. Visit any tab, any tree node or any catalog item *before* unchecking WOW64 File Redirection. This will prevent the crash.

Hope this helps, Don. Let me know if you want any of my configuration/settings files.

-Jeff

Okay, my theory is that starting up on "MyComputer" is the crucial point. Can you, or anybody else, confirm this? I assume, XY attempts to load a 64-bit module when the first file browsing happens after WOW64 redirection is disabled.

Confirmed. When I start XY at any other location besides "Computer", the crash does not occur.

-Jeff

[noir]

i can confirm

here is how to reproduce it, enable minitree (click on computer - but leave a drive like C: in the minitree list) close XY, reopen XY (it will start on computer) - disable wow 64 and then click on c: (or open in new tab) it will then crash

error message
ﾌｧｲﾙが見つかりません:
File is not found. :netapi32

[admin]

This would mean there might be another bug: When you start XY on C:\Windows\System32 AND have WOW64 Redirect disabled you should get the listing of the wrong C:\Windows\System32 because the WOW64 Redirect disabling happens only later in the start up procedure! Can you confirm?

[Jeff Bellune]

This would mean there might be another bug: When you start XY on C:\Windows\System32 AND have WOW64 Redirect disabled you should get the listing of the wrong C:\Windows\System32 because the WOW64 Redirect disabling happens only later in the start up procedure! Can you confirm?

When I start XY on System32 and WOW64 Redirect disabled, XY first loads SysWOW64, then immediately switches to System32. On my system, the switch happens really fast and is not noticeable unless you are watching for it. On slower systems it may be more noticeable.

I guess the important thing is that XY gracefully handled the folder switch without crashing.

-Jeff

[admin]

This would mean there might be another bug: When you start XY on C:\Windows\System32 AND have WOW64 Redirect disabled you should get the listing of the wrong C:\Windows\System32 because the WOW64 Redirect disabling happens only later in the start up procedure! Can you confirm?

When I start XY on System32 and WOW64 Redirect disabled, XY first loads SysWOW64, then immediately switches to System32. On my system, the switch happens really fast and is not noticeable unless you are watching for it. On slower systems it may be more noticeable.

I guess the important thing is that XY gracefully handled the folder switch without crashing.

-Jeff

Surprises me! I have nothing to do with this folder switch... Do you have auto-refresh enabled? If yes, please try again without auto-refresh.

[Jeff Bellune]

This would mean there might be another bug: When you start XY on C:\Windows\System32 AND have WOW64 Redirect disabled you should get the listing of the wrong C:\Windows\System32 because the WOW64 Redirect disabling happens only later in the start up procedure! Can you confirm?

When I start XY on System32 and WOW64 Redirect disabled, XY first loads SysWOW64, then immediately switches to System32. On my system, the switch happens really fast and is not noticeable unless you are watching for it. On slower systems it may be more noticeable.

I guess the important thing is that XY gracefully handled the folder switch without crashing.

-Jeff

Surprises me! I have nothing to do with this folder switch... Do you have auto-refresh enabled? If yes, please try again without auto-refresh.

Same result with AutoRefresh disabled.

-Jeff

[noir]

same here. starting with wow64 disabled , it loads the syswow64 contents in system32 first then quickly switches.

when in wow64 enabled system32 stays with the syswow64 contents.

[admin]

This is mysterious. I cannot do anything about this issue at the moment. I just can say this: If you disable WOW64 redirection you may see some side-effects. Handle with care.