jv16 PowerTools 2010 Beta5 released!

siliconman01

jv16 wrote
siliconman01 wroteWindows 7 x64 Professional, Build 782.

Attached are two sets of pgm crash logs. The program crashes after the initial scan of data and on the attempt to restart it. The second set is on closing after a reg clean exercise.

To be clear: the program now starts up correctly, but after the Initial Setup there is a report of crash when the program is restarted? In other words, the program crashes when closed?

1. This is on the first run following the installation. The cache data is collected.

2. The message is issued that the program will now be restarted.

3. After clicking on OK, the programs does not close.

4. The crash alert is promptly issued.

5. When I click on "Close Application" in the crash alert box, the application does NOT close. The alert message box does close.

It almost appears that this crash alert is being falsely issued because the program continues to run and appears to be fully functional. For example, I can do a Registry Cleaner run with no problems.

jv16

siliconman01 wrote

1. This is on the first run following the installation. The cache data is collected.

2. The message is issued that the program will now be restarted.

3. After clicking on OK, the appears program to restart.

4. The crash alert is promptly issued.

5. When I click on "Close Application" in the crash alert box, the application does NOT close. The alert message box does close.

It almost appears that this crash alert is being falsely issued because the program continues to run and appears to be fully functional. For example, I can do a Registry Cleaner run with no problems.

This is exactly what I expected: after the Initial Setup the program restarts. In other words, the program launches itself again, and then closes itself. During the closing of application's first instance it crashes, but the second, just started instance keeps running. Therefore nothing happens when you click to Close the application, and why it seems like it is a false report.

But it's not, it's just that the original instance of the program that is already hidden has crashed.

Anyhow, here is the next build:

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

It attempts to address the startup problem in which the program doesn't start at all (and shows a crash message).

siliconman01

Windows 7 x64 Professional, jv16 Build 783.

1. On installation, the program starts and builds the initial cache.

2. The message is issued that the initial setup is complete and the program needs to be restarted.

3. After clicking on OK, the program closes and restarts.

4. The crash alert box is promptly issued.

5. When clicking on "Close application" in the crash alert box, the program does not close. The crash alert box does close.

6. The program appears to be fully functional.

Ah... I think the crash alert box is coming from the initial closing of the program after click on OK to restart the program...not from the restarted program....as you previously pointed out. Not enough coffee consumed yet :)

elit3ch.ksp

Version 783 still crashed at statup (Win7 x86 Simp-Chinese)

debug log and crash log attached.

Are this related to Non-English version of Windows?

jv16

siliconman01 wrote

The old problem of data caching accessing disks that are in the global ignore list is back. This is SearchDirs.dat which includes the G:\ drive that is in the Global Ignore list of disks.

You are correct, this problem is now fixed. Thanks! The next released build will contain the fix.

elit3ch.ksp

And if the crash happens (with that crash tool window), if I create DMP file and terminate the process directly (at task manager), Ver 783 will function like this:

When I start the program, the GUI will appear then disappear, with its process terminated without any error.

if I copy DebugMode.dat to the installation folder, crash tool will appear again...

BTW: Do you need that DMP file?

jv16

elit3ch.ksp wrote

BTW: Do you need that DMP file?

No need, thanks anyway!

jv16

elit3ch.ksp wrote

Are this related to Non-English version of Windows?

I don't think so, I can't see how that could be possible. But I will find a solution for this, don't worry.

john-e34

Hi Guys, May I ask if it is possible to run jv16PT without the new debug engine...

From what I can see, the initial scan is active, right up until the debug window opens,

at which point jv16PT stops responding.

I have tried every beta-5 version, and cannot get past the initial scan.

Hence my question, are we testing jv16PT or the new debug engine? - as beta-4

worked almost perfectly...

jv16

John-E34 wrote
Hi Guys, May I ask if it is possible to run jv16PT without the new debug engine...

From what I can see, the initial scan is active, right up until the debug window opens,

at which point jv16PT stops responding.

The next released beta build will not automatically open the Debug Window.

John-E34 wrote

Hence my question, are we testing jv16PT or the new debug engine? - as beta-4

worked almost perfectly...

Well, there are thousands of changes between the Beta4 and Beta5, and we also changed to a newer software development environment. It's not just the Debug Window that was added.

jv16

Here is the most recent version:

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

It contains some more debug code in attempt to locate the bugs relating to the program crashing when started (on some systems).

Here is the official Change Log:

Issues Fixed (since the original Beta5 release) 185. File Tool: “Mass file rename” function gets an access violation (AV). 186. File Tool: “Mass file rename” window's buttons lack the colored icon. 187. File Tool: “Mass file rename” window's icons do nothing when clicked, perhaps due to the AV. 191. File Tool: the “Execute” icon does nothing. I expected it to open a .txt file in notepad. 192. File Tool: the “View” icon gets an access violation (AV). I expected it to open a .txt file in notepad. 1. Detection of some program data (such as Temp Dirs) does not honor the Global Ignore List. 2. Registry Cleaner>Most Aggressive Mode. The registry cleaner is improperly parsing Environmental Variables in HKLM\Software\Microsoft\Windows NT\CurrentVersion\SeCEdit. The exported registry key is attached. 3. The About window mentions a trial period of 30 days, although the Beta5 gives the user a trial period of 60 days. Improvements Done: 1. Improved the support for the Global Ignore List.

Due to the rather serious nature of the fixed bug #2, I would recommend all users to update to this version. I have also replaced the original Beta5 version in our server with this updated build, so all the new users downloading the beta will automatically get the 784 build.

max_ita

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.

leonardo

With Win-XP-Prof SP3 (Dutch language) the jv16PT2010 build 784 freezes too in the task "Performing Initial Setup"

I let the program run for about 6 minutes. CPU usage in that 6 sec timeframe varies between 0% and 1%!!

jv16PT_debugLog.zip and Bugreport.zip are attached.

siliconman01

Windows 7 x64 Professional, jv16 Build 784.

Crash following initial setup scan.

greenag

Don't start anyway

jv16

greenag wrote
Don't start anyway

Could you please also send Debug Log of this? Instructions how to create a Debug Log are posted previously to this thread. Thank you!

siliconman01

Windows 7 x64 Professional, Build 784.

In Settings, the "Don't use central server" setting will not stay selected.

greenag

jv16 wrote
greenag wroteDon't start anyway

Could you please also send Debug Log of this? Instructions how to create a Debug Log are posted previously to this thread. Thank you!

yea, there it is

doogie

Build 784 is still crashing on exit for me.

Logs attached.

jv16

greenag wrote
jv16 wrote
greenag wroteDon't start anyway

Could you please also send Debug Log of this? Instructions how to create a Debug Log are posted previously to this thread. Thank you!

yea, there it is

Thank you very much for this, I think I got some valuable information from the Debug Log.

Here is an updated build:

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

This build attempts to fix the issue of the program not starting due to a crash, and the program crashing when closed. This build does not attempt to fix any other issues.

« Previous Page Next Page »