Page 1 of 1

Context Menu Crash

Posted: 20 Jul 2016 01:10
by TestMeister
Win 7 Prof SP1
XY Pro v17.00.0100

Just updated XY and now when right-click on any drive in the tree, XY crashes every time

Re: Context Menu Crash

Posted: 20 Jul 2016 11:33
by mnazmi
hi,

I use XY Pro v17.00.0100 and win10 64. I have no problem like you. Mine is OK. Maybe it is Win 7 or your system problem.

Re: Context Menu Crash

Posted: 20 Jul 2016 12:24
by highend
Only when you click on drives or on folders in the tree as well? Right clicking on folders in the list works fine?

Does it still happen when you use
::fresh; {ENTER}
from the address bar and try the same in that fresh instance?

Uncheck: Configuration | Menus, Mouse, Safety | Context Menus | Hide shell extensions from shell context menu

Re: Context Menu Crash

Posted: 20 Jul 2016 12:41
by LittleBiG
Set this option: Configuration/General/Menus, Mouse, Safety/Hide shell extensions from shell context menu
If the crash goes away, the problem is not in XYplorer.

Re: Context Menu Crash

Posted: 20 Jul 2016 17:53
by TestMeister
>> ::fresh;
Works fine, and appears to load a default version of XY

>> Only when you click on drives or on folders in the tree as well? Right clicking on folders in the list works fine?
Correct, folders in Tree are fine
When drives are in list view it fails as well

>>Set this option: Configuration/General/Menus, Mouse, Safety/Hide shell extensions from shell context menu
After setting this option it no longer fails

Context menu from Windows Explorer works fine though...

Re: Context Menu Crash

Posted: 20 Jul 2016 21:35
by highend
http://www.nirsoft.net/utils/shexview.html

Get this and disable all non-MS shell context menus. Reenable them one by one to find the bad one...

Re: Context Menu Crash

Posted: 20 Jul 2016 23:54
by TestMeister
I tried both 32 bit and 64 bit ShellView and disabled all non-MS Context Menu extensions but XY still crashes.
I tried reinstalling XY but no luck.
However, under Config\Shell Integration if I use the 64bit context menu it does not crash

Here is the event info:

Faulting application name: XYplorer.exe, version: 17.0.0.100, time stamp: 0x5788b870
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23418, time stamp: 0x5708a7e4
Exception code: 0xe06d7363
Fault offset: 0x0000c54f
Faulting process id: 0xb10
Faulting application start time: 0x01d1e2984223d449
Faulting application path: C:\Program Files (x86)\XYplorer\XYplorer.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 7e5cc3ba-4e91-11e6-8080-28d2447aef58

Re: Context Menu Crash

Posted: 21 Jul 2016 06:24
by highend
To make sure everything was done correctly:

Use the 64-bit version of ShellExView

Menu - Options
[x] Show 32-bit Shell Extensions
[x] Hide all Microsoft Extensions

Show a screenshot of that window after applying these settings
I need to see at least these three columns:
Extension Name, Disabled, Type

You have a 32-bit extension installed (probably together with it's 64-bit version) that "messes" with drives and works fine with Windows Explorer but not with XY...

Re: Context Menu Crash

Posted: 21 Jul 2016 07:14
by TestMeister
Based on your last post Highland, the culprit has been found...
During this last debug, I restarted XY after every toggle, which surfaced the problem extension; earlier I was not aware a restart was necessary after each toggle. Also, since this is a 32 bit extension, it does not appear in the Windows Explorer context.
However this version of Acronis was installed a year ago and had not been updated so curious as to why the error presents now.
Either way, it is a feature I can live without so will keep it disabled. Many thanks!!

Re: Context Menu Crash

Posted: 21 Jul 2016 07:19
by highend
Normally it shouldn't be necessary to restart XY after you've disabled a shell extension but nevertheless, culprit found (and that's all that matters in the end) :mrgreen:

Re: Context Menu Crash

Posted: 29 Jul 2016 01:13
by tiago
XYplorer context menu always fails to me when clicking on high zipped files count. The more items it have, the longer XY takes to recover. In some cases, 5 hours of waiting wasn't enough then I decided to force shut the program. Very unpleasant.

Win explorer takes no time on the same files.