AS hangs when opening context menu

[gn4711]

Hi Altap,

i have a problem. when opening the context menu inside salamander, the complete applications hangs without any way of reactivating.
only killing the process using procexp or taskmgr works.
the problem is reproducable.

using windows 7 ultimate, x64, quad core.

q1: is this a limitation of the missing x64 support? but i never had this problem in RC1 of windows 7
q2: is there any config/hack to disable context menus in the salamander panel?

cheers.

[Jan Rysavy]

Hi, it looks like problem with some faulty shell extension. Could you start second instance of Salamander and using menu Help > Task List > Break command break the frozen one? Bug report should be displayed, please send it to my email jan.rysavy@altap.cz.

Note: Salamander 2.52 is 32b application so only 32b shell extension are loaded/displayed in context menu. We plan to build also x64 version.

[gn4711]

sry. but this doesnt work. if clicking "break" nothing happens (after some seconds, button is active again whitout any "GUI activity").

is there any way to disable context menu or just display only a minimal - core context menu?

[Jan Rysavy]

It is possible to disable and enable (context menu) shell extensions using ShellExView.

[gn4711]

It is possible to disable and enable (context menu) shell extensions using ShellExView.

yes, i know... but i mean disabling the context in altap salamander! so it doesnt display a context menu inside the app.

[Jan Rysavy]

It is not possible in Salamander.

You should really track down the faulty shell extension and disable it or update it with fixed version.

[Ether]

You should really track down the faulty shell extension and disable it or update it with fixed version.

And post its name here, so we know what to look for next time, if possible.

[gn4711]

update: if found a nice work-around. the app only freeze when selecting context menu of a folder!!
when selecting the context menu of a file FIRST, THAN you can also get the context menu of a folder WITHOUT app freeze.
thats strange...

also. i tried to find out the context menu entry which fails. after disabling all custom / no microsoft context menu entries,
the application still fails.

[therube]

Are all folders this way or only specific ones?

Since it is affecting directories, just what is in the particular directories?
AVI files by chance?

If so, it could be (an infamous) MS gottcha. Try disabling shmedia.dll
http://support.microsoft.com/search/def ... m=1&res=20

[gn4711]

Since it is affecting directories, just what is in the particular directories?
AVI files by chance?

Thanks for your advice. But im sorry. It is independend from Folder Content. Empty, Full, only Docs, only unknown (VMWare Image Directory without installed VMWare) doesnt work. It also happens when right-clicking inside a folder on empty space (f.e. you want to create a new folder using the context menu).

For me, it is a Altap Salamander Bug not handling x64 environments correct. I will give up searching and will wait for a x64 version if it ever will come up.

[Jan Rysavy]

For me, it is a Altap Salamander Bug not handling x64 environments correct. I will give up searching and will wait for a x64 version if it ever will come up.

Be prepare that all 32bit software on your computer is potentially broken by faulty shell extension you have installed.
By using 64bit software you will not solve this problem, it will be only hidden. I don't understand why not find where the problem is?

[SelfMan]

Dowload the ProcessExplorer from Sysinternals.
Run it, start Salamander and get it to the frozen state.
Switch to ProcessExplorer, double click on salamand.exe in process list.
Go to threads tab, resize if necessary and take a screenshot.
In the thread list click on every thread containing salamand.exe and click on the [Stack} button.
Take screenshots of those lists and upload it here.

The other possible debugging solution is to use ProcDump. A command line tool also fom Sysinternals.

[gn4711]

See attached images of the process explorer stack windows.
I cant identify anything of interest, but of course, im not the specialist in analysing buggy programs / addins.

Edit: i think 5160 was the hanging thread...

[Jan Rysavy]

Edit: i think 5160 was the hanging thread...

How did you recognize it? Context menu is opened from the main thread so it should be the frozen one.

EDIT: salamand.exe+0x126512 really looks like the main thread. Strange is your stack frame, it doesn't contain salamand.exe.

[SelfMan]

The problem seems to be somewhere at the call of wow64cpu.dll (stack id 0).

Code: Select all

Wow64cpu.dll: Manages the 32-bit CPU context of each running thread inside WOW64 and provides processor architecture–specific support for switching CPU modes from 32-bit to 64-bit and vice versa.

So far it seems that there is some unknown conflict between the 32 bit application and 64 bit system.
I've googled a bit and came around a thread where one user had simmilar problems. The result - faulty memory chips. (with that I don't want to say that yours are faulty too... I don't know how stable your system is... its just a possible option)