Access violations while editing files inside of ZIP archiv

[NotMyBug]

---------------------------
Total Commander
---------------------------
Access violation at address 0040BBFE. Read of address 00000064.
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:

0040BBFE 00413E10 7E368732 7E368814

7E37A011 7E37A037 004427F5 00413E10

7E368732 7E368814 7E3689CB 7E3774B0

7E368A0E 7E37771F 7E3749C2 7E38A954

004268F4 0044005A 0065F07E 7E368814

7E368858 7E368828 7C80CED3 7E369E7E

7E3788C9 7E3788EC 7E379349 7E38A2BA

77EFE456 77EF6E6F 005F67EC 0068BD37

0068BF62 0068536D 005D268F 019334F8

7E368732 7E368814 7E368828 7E3B63FB

7E3A0851 7E3B6577 0068DF49 76333BCE

7E3BBC9A 7E3BBE88 0191DD85 7E368814

7E368858 7E368828 7E368828
Press Ctrl+C to copy this report!
---------------------------
Ja Nein
---------------------------

[NotMyBug]

Does the error occur just after re-packing the viewed file to the .xpi?

Yes.

Due to my latest findings I have to question this statement - Are you really sure that it happened *after* repackaging on your PC?
First I silently accepted your observation, even referred to it in one of my previous postings...
However, for at least one case I now can *proof* that it happened exactly at the beginning of repackaging!
http://tinypic.com/view.php?pic=2ug0vh3&s=5

The image shows the Access violation besides the just opened repackager progress window (at 0%).

[petermad]

Are you really sure that it happened *after* repackaging on your PC

No, I must admit I am not sure of that - only that it happens after I click OK when TC asks me whether I want to repack the edited file.

[ghisler(Author)]

You don't need to test any longer, I think that I found the cause now. Please re-test when beta 2 comes out. Thanks for your help!

[NotMyBug]

Thanks for *your* help!

Please re-test when beta 2 comes out.

I will do so.

[petermad]

I have not been able to reproduce the bug in TC7.50b2

[NotMyBug]

I also did a quick test, yesterday immediately when beta2 was released, and I also failed to reproduce the bug. However, I prefer to make one more thorough test as soon as my time permits: Before posting here, I want to make sure that the bug really is removed. Remember that bug sometimes did not show for many of our previous trials.

[ghisler(Author)]

I could find the cause of the bug from one of the bug traces, so it should definitely be fixed. Please report back here if you should encounter it again later, and give as many details as possible.

[NotMyBug]

Please believe me, I tried my best,
but I cannot get that damn TotalCommander to crash once more.

I tempted to say that, apparently, the bug has successfully been fixed with beta2.
Congratulations to Mr. Ghisler and the team, thank you!

Honestly, at the time of my first posting here I did not really believe that this issue could ever be eleminated. Chances were very bad because...
-that bug occured randomly
-moreover the bug was very rare, most times it did not show
-the bug seemed to be a plugin issue
-I was completely unknown to the staff here

So once more I like to thank MadPeter for trusting me and performing many tests to trigger this evil bug. Without your help no fix would have been possible.

I consider this an important fix, at least it is for me.

Bye,
NotMyBug