On an x64 Windows 7 Desktop PT Version 2.0.0.966


I'm not sure if this particular repeatable bug has been reported above. I can make it happen at will.

  • 1. In the History Cleaner results, double-click a line referencing only files (for example, Macromedia||Flash Player).


    2. You get two AVs in a row when continuing the application, then the normal List Data window for files appears.


    3. The AVs do not happen when you double-click a line referencing only registry entries.


    4. I don't know what would happen for a line referencing both (none on my system now, AFAIK).

*History Cleaner double-click Debuglog and bugreport files.zip

tullik wrote
On an x64 Windows 7 Desktop PT Version 2.0.0.966

I'm not sure if this particular repeatable bug has been reported above. I can make it happen at will.

Yes, this is exactly the problem I already reported. See: http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4183&st=0&sk=t&sd=a#p25317

Prerequisite for reproducing the 2x Access Violations in a row (and by the way the the 'property option' is not working too) is check boxing the line "Highlight selected lines" in the jv16PT Setting -> Advanced Interface:

Settings_AccessViolation_HistoryCleaner.jpg

tullik wrote
On an x64 Windows 7 Desktop PT Version 2.0.0.966


I'm not sure if this particular repeatable bug has been reported above. I can make it happen at will.

  • 1. In the History Cleaner results, double-click a line referencing only files (for example, Macromedia||Flash Player).


    2. You get two AVs in a row when continuing the application, then the normal List Data window for files appears.


    3. The AVs do not happen when you double-click a line referencing only registry entries.


    4. I don't know what would happen for a line referencing both (none on my system now, AFAIK).

*History Cleaner double-click Debuglog and bugreport files.zip

I believe this is the same issue, already reported fixed on Monday. I'll hope to get the preview build ready soon so we can verify what's fixed.

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.
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.