History cleaner fails

eckis

Vista 32bit. Have successfully used 2008. With 2009, History Cleaner search for data runs without result. Animation keeps going. Task Manager shows cpu usage. But, no results are ever shown. 2008 is still installed, and still works swiftly.

TIA,

eckis

jv16

Could you please try this with Debug Mode enabled and send me the debug log?

eckis

jv16 wrote
Could you please try this with Debug Mode enabled and send me the debug log?

I would, but I have no idea how.

I will keep checking this forum to see if anyone else shows up with the same problem. If something unique to my system is creating the problem, I'll just keep using 2008.

Thanks,

eckis

Oh, the power of instructions. RTFM still rules.

Thanks again.

eckis

Debug Log of jv16 PowerTools

If you think the following debug log shows a bug or a crash in the product, Please post this log file and a description of the problem to Macecraft Software's forum. All users who help us to solve problems in our product will receive a free personal license for the product!

* +++ App Init Start +++

--clip--

eckis

Still fails. DeBug script posted above on March 31.

Animation icon still spins. Progress bar advances to just beneath the w in awhile (on the "might take a while" message.) Hardrive action according to the flickering led. No completion.

I have let it run as long as an hour with same result.

All other functions appear to work as they always have with 2008.

Vista 32bit Windows Vista Home Premium Service Pack 1 (build 6001) 2.00 gigahertz AMD Athlon 64 X2 Dual Core

Thanks

redseujac

In the future you could export all that to a text-file, zip it and then upload it here as an attachment.

That way you could prevent making very long posts like the one above :

jv16

And the Debug Log above doesn't include any actions of History Cleaner, so could you please create a new one and while in debug mode open the History Cleaner so its data is also included to the Log file.

eckis

I've zipped both logs.

Thanks,

eckis

redseujac

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

Thank you very much for sending the log file, now I can see what's most likely causing the problem. The issue should be fixed in the next released version due out later in this month.

I say "should be fixed" because I cannot reproduce the problem and therefore I cannot be absolutely sure if I nailed it.

redseujac

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.