XYplorer Beta Club

Some names of files I have at my drive are very long, i.e. 139 or 144 symbols(spaces included). The path to them is quite long as well: 82 symbols (slashes included). However 144 + 82 << 255, and Explorer or Total Commander does not have any troubles with them.
But when Tracker finds after searching those files, it is not possible to fulfill any command from context menu; every attempt finishes surely by app's crash
(AppName: trackerv3.exe
AppVer: 3.50.0.121
ModName: qvpse3.dll
ModVer: 7.0.0.1
Offset: 0000582b)
I am not sure if the cause of problem is just filename lenght, but it seems to be this.

QVPSE3.dll appears to be part of QuickView. Check google groups to see that this file is known to cause crashes.

Generally, crashes after opening TrackerV3's context menu have always (ie since TrackerV3 exists) proved to have been caused by poorly written custom shell software or other software mocking with the shell's context menus.
Why now do Explorer and various replacements sometimes appear more tolerant than TrackerV3 to this stuff? Because the stuff was written to work under Explorer, and many replacements just build a nice skin around Explorer's core functionality. TrackerV3 is different: here everything is hand-made from scratch. It's not an Explorer clone!

Yes, you are right, this QVPSE3.dll is indeed a file of Quick View Plus installed at my system. I do trust you that this file may threaten system stability and be the cause of application crash when opening a file from Tracker by QVP. But I don't understand, how QVP can interact Tracker internal commands executing, i.e. "copy filename to clipboard" or "copy file to..." etc.
And why this QVP does not crash Tracker when full filename is shorter then <<< 200 symbols?
And, the most important question, is there any solution for this problem?

Leopoldus wrote:But I don't understand, how QVP can interact Tracker internal commands executing, i.e. "copy filename to clipboard" or "copy file to..." etc.

Hard to say from the distance (I don't have QVP). Does it crash on every internal (external, too?) command?

Leopoldus wrote:And, the most important question, is there any solution for this problem?

Sure: remove QVP.

Does it crash on every internal (external, too?) command?

I don't sure about every internal and external command, but all those internal and external I've tested (more then 10) does.
I think the result does not indeed depend on the selected command at all. If I only open context menu to this file - and then close it without selecting any command, the result is the same: the app crashes after I press [Escape] key to close context menu.

Leopoldus wrote:I think the result does not indeed depend on the selected command at all. If I only open context menu to this file - and then close it without selecting any command, the result is the same: the app crashes after I press [Escape] key to close context menu.

So, QVP is indeed not interacting with Tracker's internal commands but just doing something nasty to the context menu. I can't do anything about it.

Well, I understand, that you can not respond for QVP-caused problems. But have you any idea explaining what happens there? Am I right, that the cause in somehow in finename and/or file path length?

Leopoldus wrote:Am I right, that the cause in somehow in finename and/or file path length?

It appears so. If that's the only behavior pattern you can see then there must be some connection to the file name length.

Do the filenames or pathnames contain non-alphanumeric characters? I've know applications that have problems with such characters, although I'm not aware of TrackerV3 having any such problems, they may be upsetting an external application (i.e. QVP) when they are passed to them.

Leopoldus, I changed something concerning the context menu in the current BETA. A mere shot into the dark. Just curious: does the problem still exist?

Donald

Sorry, but the problem persists.

There was a lot of non-alphanumeric characters (commas, dashes, spaces, brackets, ampersand) in the files and the folders names, but even when I removed all of them (e.g. spaces) from the file full name, the problem was in place.

I've cheked this bug at another system without QVP, there was no any problems there. So it's a problem of TrackerV3 and QVP conflict.

Leopoldus wrote:... So it's a problem of TrackerV3 and QVP conflict.

Well, the world is full of conflicts. This one we gonna have to live with.