updates

[south37]

With an archive open, pressing the key matching the first file name character to jump to the first matching file, causes a PowerArchiver crash.

i.e. if a file in the archive is “THEFILE.TXT” (first starting in T) then pressing the letter ‘T’ sets the focus in the list to that file but immediately puts up a dialogue box with “PowerArchiver 2017 has stopped working” . This is a Windows dialogue and says: “Windows will close the program …”.
Happens in large and small archives. Checked in .zip and .rar

[spwolf]

@south37
Please check your issues with latest build:
PA 2018 18.00.30: http://dl.powerarchiver.com/2018/powarc180030.exe

and let us know if your issue has been fixed. Thank you!

[spwolf]

@south37 is this with PA 17.01.04 or earlier release?

[spwolf]

@south37 i assume you are using latest one… can you please send your settings (Options> ) to support at conexware dot com, so we can check with your exact settings.

We had this reported few versions back, cant reproduce it here right now. Thanks!

[south37]

I have emailed the settings file.

The version I am using is 17.01.04

[spwolf]

@south37 hm, seems to work fine on my laptop. What OS are you running? Nice settings!

[south37]

Windows 10 64bit Ver 1511 Build 10586.0

[spwolf]

@south37 same here. Lets see if @Mili can reproduce it in the morning. Thanks!

[south37]

The Windows crash log “Report.wer” says:

Sig[0].Name=Application Name
Sig[0].Value=POWERARC.EXE
Sig[1].Name=Application Version
Sig[1].Value=17.1.4.0
Sig[2].Name=Application Timestamp
Sig[2].Value=59d2a005
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.10586.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5632d193
Sig[6].Name=Exception Code
Sig[6].Value=c0000005 <-- This is an Access Violation I believe
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000348ae

[spwolf]

@south37 unfortunately without debugger running, windows log is not useful to us. Once we can reproduce it on development machine, we can usually see exact code causing the issue.

[Mili]

tried reproducing here as well with the settings, no luck.
does it occur on one specific file or all files?

If it’s on a specific file, could you send it please?

thanks

[south37]

It occurs on all files. I created a small archive with test text files and the error occurs on that as well as on larger archives.
So it is not the file itself but something else.

The only clarification I would make is that I initially said that the crash happens immediately after pressing the key. In fact it takes about a second or two before the crash occurs. After pressing the key to jump to the file, I can still move up or down in the file list with the arrow keys before the crash occurs. If I press the arrow keys quickly enough the crash is delayed quite a while and occasionally does not occur at all. But I can’t use the 1st char jump method to select another file before the crash occurs.

[spwolf]

@south37 Can you try exporting HKCU\Software\PowerArchiverInt and sending it over please? Then try using Options> Reset to Default and see if this issue still happens for you.

You can recover your settings by running that reg of course.

Maybe some setting that causes issue is not exported via Options.

much appreciated!

[south37]

I have exported the registry keys and emailed them.

After resetting to installation defaults, the problem is still there. PA crashes still.

[cporeaux]

Hi,

I encounter the same issue ;-(

• On my pro laptop (Windows 7) or my personnal desktop ( Windows 10 Redstone 2).
• I’m admin on both of computers;
• Normally registered user for both Windows and PA;
• Problem with RAR ou ZIP compression format, not seems to be linked with file, but HCI only;
• Same issue if preview panel is opened or not;
• Windows settings on my desktop PC : desktop folder is not on default folder.

My way to reproduce :

1. I open a RAR file [with one folder (and many things in it)];
   The folder is beggining with digit 1;
2. I just click on the key ‘1’ and after 1 or 2 seconds, Windows pop-up with failure

What explains south37 is exactly what i have too : if i use a zip file with many entries, i can type one letter, and PA jump to the correct item, and i can still move till app crashes.

.
.
Using Procmon from sysinternals.com, i saw a result ‘Invalid PARAMETER’ trying to read Data/list directory.
Last event is making a QueryOpen on ‘PowerArchiver 2017.lnk’ on my desktop with a Result Name not found. (i d’on’t want/checked th desktop shortcut).

I sent an e-mail with procmon log file (sorry, french info in zip)

Maybe with this it’s better to fund the issue ?

[Mili]

thanks very much for sending over the information @cporeaux

We still have not been able to reproduce the issue and it is essential that we reproduce it.
Could you please send us a sample file that reproduces the error for you?

We hope to then reproduce it here so we can log it in for fixing.

Thanks!

[cporeaux]

Hi,

So it should be linked with the environment and not the compressed file only ?
I’ll send you a very short file, the problem does occur with it also.
If you have any other test to do or if you have a version to have more log for you, still no pb.

Regards

[spwolf]

@cporeaux we were able to reproduce this issue on Win7 x64 image… but not on others, very interesting. Hopefully we can fix it soon enough.

thanks again!

[spwolf]

@cporeaux Can you please check with following release and let us know if the problem is still there:

New version: PowerArchiver 2018 18.00.23 - BETA 1
Download: http://dl.powerarchiver.com/2018/powarc180023.exe

thanks!

[south37]

Just installed and tested the new beta on my desktop machine and the crash still occurs.

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

Just installed and tested the new beta on my desktop machine and the crash still occurs.

thanks for letting us know… i was aware that nothing specifically was done for this, but lets see in next releases. How does 2018 feel otherwise? Thanks.

[south37]

@spwolf I didn’t keep it installed too long. It looks ok, but when I tried to edit a text file from an archive it didn’t prompt me to update the archive even though the option (under Miscellanous) “Ask to update if file has been changed” was checked.

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

@spwolf I didn’t keep it installed too long. It looks ok, but when I tried to edit a text file from an archive it didn’t prompt me to update the archive even though the option (under Miscellanous) “Ask to update if file has been changed” was checked.

did you by any chance click on X on Window to close PA when that happened (or did not happen?)

thanks,

[south37]

@spwolf Yes I would have closed the archive with the X on the RHS of the window.

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

@spwolf Yes I would have closed the archive with the X on the RHS of the window.

i think that has been written in this morning… in general, since now there are multiple tabs possible and it also supports archive inside archive editing and saving, closing on the tab works (could be used as a workaround).

thanks!!!

[south37]

@spwolf I am a bit confused. The old behaviour was that when a file was changed (eg editing a text file with Notepad) PA would detect the change to the file in the temp file directory and immediately prompt the user whether it should be updated in the archive. It didn’t wait until the whole archive was closed.

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

@spwolf I am a bit confused. The old behaviour was that when a file was changed (eg editing a text file with Notepad) PA would detect the change to the file in the temp file directory and immediately prompt the user whether it should be updated in the archive. It didn’t wait until the whole archive was closed.

there were a lot of changes there since now it tracks multiple files in multiple archives, including archives that are inside archives.

It is a bug, not a intended behavior, we need to detect changed files at X from complete archive, not just the tab.

thanks!

[south37]

@spwolf Sorry to be persistent. The behaviour in PA2017 and earlier was that as soon as a file being edited or modified from the archive was changed (eg saved to the temp directory) PA would detect that and give a popup dialogue box asking to update the archive with the modified file. From there the archive was still open. If the new behaviour is to update changed files only when the archive (or tab) is closed, I think this is a backward step. This probably needs a new thread!

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

@spwolf Sorry to be persistent. The behaviour in PA2017 and earlier was that as soon as a file being edited or modified from the archive was changed (eg saved to the temp directory) PA would detect that and give a popup dialogue box asking to update the archive with the modified file. From there the archive was still open. If the new behaviour is to update changed files only when the archive (or tab) is closed, I think this is a backward step. This probably needs a new thread!

What’s the difference from your usage point of view? Instead of notifying you each time when you change each file, it does it at the end?

[spwolf]

I can move it to another thread later on, so no worry’s there.

Thanks.

[south37]

@spwolf The difference is that it gives me more confidence that the edited file has been updated correctly. If the archive is open for some time and the file is not updated I might forget about it - if the computer is rebooted with PA open, or PA is closed unexpectedly etc then the pending save will not be completed. What if a number of files are edited, will PA2018 update all of them on closing the archive? Indeed with the issue in this thread not being resolved (1st char jump crash) this would result in the modified file not being updated (although perhaps it is only for me and @cporeaux!). I take it that preserving the old behaviour of the immediate file update can no longer be done.

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

@spwolf The difference is that it gives me more confidence that the edited file has been updated correctly. If the archive is open for some time and the file is not updated I might forget about it - if the computer is rebooted with PA open, or PA is closed unexpectedly etc then the pending save will not be completed. What if a number of files are edited, will PA2018 update all of them on closing the archive? Indeed with the issue in this thread not being resolved (1st char jump crash) this would result in the modified file not being updated (although perhaps it is only for me and @cporeaux!). I take it that preserving the old behaviour of the immediate file update can no longer be done.

it does tell you for each file, so you know it has been updated. Lets fix the X on main window detection and then you can see how you like it. And we can move from there.

thanks!

[spwolf]

@south37 please check latest release:
Download: http://dl.powerarchiver.com/2018/powarc180029.exe

Check both updating and selecting character in file list.

Thanks!

[guido]

could this be related to the preview window in combination with a virus scanner?

[guido]

Also, did someone run processmonitor during the action?

[spwolf]

@guido said in PA crashes when using 1st char to select file:

could this be related to the preview window in combination with a virus scanner?

nope, vcl buggies.

[south37]

PA no longer crashes when selecting a file with the first character but the function does not always work.

Sometimes pressing the first letter of a file causes the selector to jump to the appropriate file but it does not always function.

It appears to be that when the target file is not visible in the file-list window, the selection does not move to the file name starting with that letter. Sometimes not when it is visible also, or only after a few key presses! I can’t work out the pattern exactly. Once a jump has been successful it works the next time even if files with that starting letter are out of the visible window.

Edited file updating now works again - updates immediately after changed file is saved.

[Mili]

thanks @south37
Tested it, when 1st character stops responding, move the scroll bar up or down just a bit and it works again.
Logging it in.

[spwolf]

@south37
Please check your issues with latest build:
PA 2018 18.00.30: http://dl.powerarchiver.com/2018/powarc180030.exe

and let us know if your issue has been fixed. Thank you!

[south37]

Just tested the 1st char select with version 18.00.31. It is working correctly.

[spwolf]

@south37 said in PA crashes when using 1st char to select file:

Just tested the 1st char select with version 18.00.31. It is working correctly.

thank you very much for the report and follow ups