tc75b3 bug in Lister/LinkInfo.wlx

[Aleksio]

1. The AV has occured when opening Lister on *.lnk file. I have LinkInfo.wlx plugin installed.
See stacktrace below.

---------------------------
Total Commander
---------------------------
Access violation at address 6BD380F9. Read of address 6BD380F9.
Please report this error to the Author,
with a description of what you were doing when this error occurred!
Continue execution?

Windows exception: C0000005

Stack trace:

6BD380F9 0041C418 004446E7 00444730

004417D5 004435DD 004159F8 00442A48

00443322 00413DDC 7650C6C0 7650C798

7650C741 76501D54 76501D7A 004429ED

00413DDC 7650C6C0 7650C798 7650C741

765035CD 765053EA 764FAB24 004192B4

0041936E 0041A2FE 004193C0 0041957A

006931C4 75AE0237 772C1E9C 772C1E6F


Press Ctrl+C to copy this report!
---------------------------
Yes No
---------------------------

2.
After this, I opened *.txt file (with default SciLister.wlx plugin). It worked fine. I can switch to standard text view - also works fine.

3. I repeated step 1 (pressing F3 on *.lnk file), and I've got the following:

---------------------------
FILEINFO_WLX
---------------------------
Fail to Load RICHEDIT library
---------------------------
OK
---------------------------

4. I repeated step 1 again on identical (same byte-to-byte) and different *.lnk files, and the Lister opened fine, but I've got the exception from step 1 after closing the Lister with ESC key.

[fenix_productions]

2Aleksio
1. Which LinkInfo version do you have? 1.5.1.0 works here without any problems.

2. Does it happen for all LNK files or specific ones?

3. Did you restart TC after AV? I assume that you decided to continue execution. In such case "something" is still wrong and TC can crash with other plugins even if they are OK (in your case FileInfo).

[Boofo]

I can confirm that version 1.51 works fine here with no problems.

[Boofo]

2Aleksio
Make sure you have unaspack.dll in the fileinfo plugin directory. Sounds like you have a couple plugins fighting.

[fenix_productions]

2Aleksio
Please, check TC with clean INI file and without other applications running in background.

2Boofo
It doesn't mean "fighting".

If you have bug in one plugin it's not always the case for immediate crash. Sometimes it takes few seconds / minutes to see an error. IMHO LinkInfo is the culprit. It corrupts memory and waiting to crash: either right away or after a while*.

To be 100% sure Aleksio can switch LinkInfo off and use TC little bit longer.

*) I saw such behaviour while writing my own plugins. TC was crashing on some files after years of correct work. Obviously: my plugs was the source of problems even if there was no message indicating it.

[ghisler(Author)]

The problem with list plugins is that once they have been created, they are working on their own - they aren't called by Total Commander functions, but get Windows messages like resize etc. Therefore TC cannot detect in which Lister plugin a crash occurs...

[Boofo]

2fenix_productions,
As with any coded program/plugin, there is always a potential of one conflicting with another. It happens in Windows all the time. That is what I was referring to.

[ghisler(Author)]

2Aleksio
Do you still get this plugin with updated LinkInfo plugin and TC 7.5 beta 4?

[Aleksio]

2Aleksio
Do you still get this plugin with updated LinkInfo plugin and TC 7.5 beta 4?

From HISTORY.TXT:

27.05.09 Fixed: Access violation in icon thread when closing TC with open separate tree (fix should also improve the general stability)

I hoped the problem gone, but I still was getting the exception win TC 7.5 beta.
But the problem was solved after updating LinkInfo.wlx from 1.5 to 1.51.

Version 1.51 (of LinkInfo):
1. One very annoying bug was fixed: on some computers closing Lister window resulted
in closing Total Commander itself.

So, it is just magic that LinkInfo worked fine for me with TC 7.0.

Thanks for attention!

[ghisler(Author)]

Great, thanks for your feedback!