An unhandled exception occurred at...
Free Zip software and Rar extractor
Brought to you by:
giorgiotani
Originally created by: projekt....@googlemail.com
What steps will reproduce the problem?
1.when I close the program
2.
3.
What is the expected output? What do you see instead?
An unhandled exception occurred at $0000007FEFC351757:EAccessViolation:Access violation $000007FEFC351757
What version of the product are you using? On what operating system?
PeaZip releast 5.0.1 win64 Build
Please provide any additional information below.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
I've attached a build of peazip.exe (to replace the application's main executable) compiled with a prior version of the IDE, Lazarus 1.0.6.
Can you kindly test if this fixes the problem you are experiencing?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
Various changes were made in 5.1.0 release to prevent possible access violation causes, does the issue still happens?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
(No comment was entered for this change.)
Mergedinto: 245
Status: Duplicate
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: j...@mmcc.com
I, too, have this problem, and upgrading to 5.1.0 x64 version did NOT fix it.
The program works fine until you try to exit it. Doing so, even if you did absolutely nothing but launch and then exit, causes it to display that error (address differs each time). Clicking “Cancel” or the close button on that dialog causes it to re-appear with the same error but different address appended to the previous message. Attempting to close it again causes it to appear yet again, now with a third copy occurrence of the message (with different address) appended after the other two, and so on and so on until the dialog has grown too tall to fit on the monitor.
The only way to exit it is to force-quit the “peazip.exe” process in Task Manager or Process Monitor or some such. (End Task in Task Manager’s Applications pane will NOT suffice! It merely causes yet another copy of the error message to be appended to the dialog.)
Running Windows 7 Pro x64.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
(No comment was entered for this change.)
Mergedinto:
Status: Started
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
Thank you for reporting, issue has been reopened for testing.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
The issue cannot still be replicated on my test machine, so I've attached an experimental executable, that can be used to replace peazip.exe in program's folder for testing purpose.
The test program will show a message from stage 1 to stage 5 when the program is closed, allowing to understand what is the procedure in error on the machines running in this issue.
Please feel free to add any other suggestion about how replicating the problem.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
New 5.1.1 release should improve the way this error is handled, but since I'm not able to catch it happening on my test machines I'll let the issue open for more information.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: guijarre...@gmail.com
In my case, I am running a Windows 7 32 bits with Peazip 5.1.1, and when I trying to open any compressed file, I get this error:
"Access Violation"
If I click OK, Peazip opens but it freezes my desktop. Also, I have another network issue. It disconnects my interface network.
If I click on cancel, I had another error message:
---------------------------
Error
---------------------------
An unhandled exception occurred at $0067A76B :
EAccessViolation : Access violation
$0067A76B
$7700C4E7
$7700C5E7
$77004F0E
$77004F7D
$76EF702E
$0040B442
$004139D8
$0040DA98
$0064FDD9
$00551AB0
$006098DD
$005C774A
$0064EC3A
$0064C31C
$0041FC40
$004238A4
---------------------------
Aceptar
---------------------------
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: giorgio.tani.software@gmail.com
This seems a separate issue from the one regarding error in closing the application, can you please provide me a file triggering the error when you open it, and peazip's conf.txt file?
conf file can be found from main menu, options, settings, general (2) tab, there is a link to the folder containing PeaZip configuration files, and it can be uploaded here or sent to support mail giorgio.tani.software@gmail.com
That may help me understanding what happens with the network; the software should just enumerate system's disk units using standard Windows api, that may also be network unit, but the beavior reported should definitely not happen.
Hi,
i tested the v5.2.2 and it seems to me that the problem is history.
Great job :-)
/*/thumbs up*\
Duke
Hi,
I am still getting this with 5.2.2 :(
Exactly the same as the OP. Just opening peazip and trying to close it is enough to cause the Access violation and the only way to then exit is via the task manager.
Richard
Hm, in my case I could prevent the error on versions before 5.2.2
if I startet Peazip with rightclick and "Run as Administrator...".
If I did so I could close the program normally.
Does this help in your case ?
If not, there seems to be a second problem resulting in the same/related error behavior.
Duke
Indeed, if I start peazip like you say with rightclick and "Run as Administrator" then I do not have the issue i.e. the program closes normally. I think this means we have the same issue. I have a 12 core i7 with 24Gb RAM if that is of any interest is seeing how our machines are different.
Richard
My machine is a AMD Phenom II X4 with 8GB RAM, Win7 64Bit
and .... x86(!)-Peazip 5.2.2.
After I realized that I have uninstalled the x86 version and installed
the 64 bit version and .... I got the error !!!!
Now I have the x86 version installed again and it works !
Seems we have to stay on x86 version at the moment.
Duke
Thank you for testing the issue further, I'll try to replicate the error on my Win7 64 bit machine with 64 bit version to understand better what happens and why running as administrator seems avoiding to the problem.
I have the same problem, but only with the 64bit version. And it happens everytime when I created (or extract) a archive or closing the program.
No fix for this bug?
I've removed various conditions that might have triggered similar error in past releases and updated the compiler since first report, but I'm still unable to reproduce this bug on my test machines, anyway I'll try to spot what causes this issue to trigger this error.
Thank you! This one is very annoying.
Hm, since 5.3.0 Peazip is running stable on my system as 64bit version.
Before I had exactly the same problem ...
Not for me. :(
Anything new about this?
Team of Lazarus/FPC (compiler used to build PeaZip) recently acknowledged a problem with the WIN64 compiler that may trigger issues on 64 bit systems, I'll apply their recommendation to fix it:
http://wiki.lazarus.freepascal.org/Windows_Programming_Tips#FPC_2.6.x.2FLazarus_warning_.28Missing_support_for_SEH.29
Not being able to reproduce the crash on my 64 bit test machines, I cannot confirm if this is the real source of the problem.
Thank you!