Is anyone here able to crash PowerTools 2010 at will? That is, if you perform a certain task, does PowerTools always or usually crash? If so, please report in here.


We are working on this issue and we will shortly have a small test application for you guys to try out.

Yes, I can crash jv16PT 2.0.0.966 easily with changing 'Settings' and using 'History Cleaner'

see: http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4183&st=0&sk=t&sd=a#p25317

Regulary I get an application error 'Freeze' when closing jv16PT 2.0.0.966 after doing some actions with 'History Cleaner',

see http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4183&st=0&sk=t&sd=a#p25308

Leonardo wrote

Yes, the test program does creates an access violation.

Great news! Now we are able to finally reproduce the pesky little problem. I believe this is the same problem many users, such as Hanzie, reported here.


Now that we can reproduce the problem, we should be able to fix it. Please stay tuned for a new version of the same test application that this time shouldn't crash (because the bug is fixed).

Every time I run a 'Clean & Fix' I get application crash with error 'List out of bounds'.

Similar to Leonardo I also get crash after using history cleaner when closing application with click on X in top-right corner.

jv16 wrote
Leonardo wrote

Yes, the test program does creates an access violation.

Great news! Now we are able to finally reproduce the pesky little problem. I believe this is the same problem many users, such as Hanzie, reported here.

Do you think there is a correlation with the application error 'Freeze' when closing jv16PT build 963/964/966 as reported by several users, me included?

Leonardo wrote

Do you think there is a correlation with the application error 'Freeze' when closing jv16PT build 963/964/966 as reported by several users, me included?

It could be related. The Access Violation problem relates to a list of pointers getting mixed up somehow, and when these pointers are accessed an Access Violation can occur. If such pointer that no longer points to the right place happens to point to a place within the program, it could be accessed without Access Violation and that could cause the freeze.


We will know soon.

jv16 wrote
Is anyone here able to crash PowerTools 2010 at will? That is, if you perform a certain task, does PowerTools always or usually crash? If so, please report in here.


We are working on this issue and we will shortly have a small test application for you guys to try out.

Yes, One of my old software applications on my system was a version of Creative Sound Blaster. This has long been removed. But If I look for "Creative" or "Creative Tech" as a search word in Registry Finder, it will find approx. 2200 errors and crash PT 2010.

charlesn56 wrote
jv16 wroteIs anyone here able to crash PowerTools 2010 at will? That is, if you perform a certain task, does PowerTools always or usually crash? If so, please report in here.

Yes, One of my old software applications on my system was a version of Creative Sound Blaster. This has long been removed. But If I look for "Creative" or "Creative Tech" as a search word in Registry Finder, it will find approx. 2200 errors and crash PT 2010.

What kind of crash do you get? Please explain a little bit more. Are you using jv16PT 2.0.0.966 (or 961/963/964) and which Windows OS?

Jouni,


Please put me on the list for the impending private test build. :

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

Here is the preview build:

http://www.macecraft.com/downloads/betas/jv16PT2010_build967.exe


And here is the Change Log:

Bug fix: the program can randomly crash to "List Index Out Of Bounds" error when working with the result lists, such as with the results of the Registry Cleaner.

Bug fix: the program can randomly crash to "Access Violation" error when working with the result list.

Bug fix: Decrypt feature of File Tool's More Functions menu actually executes file Encrypt, not Decrypt.

Bug fix: In History Cleaner, if you double click an item, select the Files tab and select Properties from the Right-Click menu, nothing happens.

Bug fix: If you select not to install certain translations (e.g. Russian or Dutch), they are still installed to your system.

Improvement: The installer will from now on remember its previous settings, so when installing the next update you will not have to make all the same changes again.

So, if the build 966 crashes with your computer, can you please check out and report if this one also crashes? Thanks!

hello,


no more crash here in History cleaner, properties, files tab !!!

Nice !!!

For both XP-Pro-SP3 and Win7 x86 Professional with build 967:


'History Cleaner' combined with the proper jv16 settings (Highlight selected lines check boxed) does not crash anymore with an access violation,

the 'Property Option' is now working too.

But immediately closing jv16PT-2010-beta967, after playing around in 'History Cleaner' for a while, stills ends in a Application error 'Freeze' :( .


After closing jv16B967, the Windows Task manager shows jv16.exe running for ~1 minute at 50% processor busy (utilizing 1 of the 2cp's), than the 'Freeze' follows. Or is the 'Feeze' not intended to be fixed yet?

here it's perfectly closing, even after using history cleaner

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

jv16 wrote
Improvement: The installer will from now on remember its previous settings, so when installing the next update you will not have to make all the same changes again.

IMO it doesn't work properly.


I ran setup with build 967 a first time, used the program, then uninstalled the program and ran setup again.


Setup did not remember the following:


1) Shortcuts: "Add icon to desktop" remains checked though it was not checked during the previous setup.

2) Translations: all translations remain checked, though only 3 of them were checked during the previous setup.