Clean & Fix - application crash (version 2.0.0.964)

aagaard

Each time I try to do a 'Clean and Fix' the application crashes (running Win7 x64).

I have reported the problem earlier via bugtracker for version 2.0.0.263 (bug: 213317) and according to bugtracker this bug should be fixed in 2.0.0.964. I am sorry to report, that this is not the case. I still got the same problem (2.0.0.964) and I have not been able to run Clean and Fix not even once.

I have reported this via bugtracker again for the new version with debuglog and bugreport attached.

leonardo

Aagaard wrote
Each time I try to do a 'Clean and Fix' the application crashes (running Win7 x64).

I have reported the problem earlier via bugtracker for version 2.0.0.263 (bug: 213317) and according to bugtracker this bug should be fixed in 2.0.0.964. I am sorry to report, that this is not the case. I still got the same problem (2.0.0.964) and I have not been able to run Clean and Fix not even once.

I have reported this via bugtracker again for the new version with debuglog and bugreport attached.

According to the developer the objective for build 964 is:

1. To bypass the 'Installation problems with certain AV products' in build 963 .

2. Safety improvement: Running the Clean and Fix my computer or File Cleaner with the safest scan option will no longer list any files relating to Windows,

nor any DLL or other executable files.

It is my understanding that hardly any other fixes are imbedded in build 964.

ADDED: see http://www.macecraft.com/news/197/

aagaard

Leonardo wrote
Aagaard wroteEach time I try to do a 'Clean and Fix' the application crashes (running Win7 x64).

I have reported the problem earlier via bugtracker for version 2.0.0.263 (bug: 213317) and according to bugtracker this bug should be fixed in 2.0.0.964. I am sorry to report, that this is not the case. I still got the same problem (2.0.0.964) and I have not been able to run Clean and Fix not even once.

I have reported this via bugtracker again for the new version with debuglog and bugreport attached.

According to the developer the objective for build 964 is:

1. To bypass the 'Installation problems with certain AV products' in build 963 .

2. Safety improvement: Running the Clean and Fix my computer or File Cleaner with the safest scan option will no longer list any files relating to Windows,

nor any DLL or other executable files.

It is my understanding that no other fixes are imbedded in build 964.

Well, I am not happy I you are right about this - this means I have to make a new bugreport all over again.

Made some remarks under another topic: http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4089#p25085http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4089#p25085

leonardo

Aagaard wrote
Leonardo wrote
Aagaard wroteEach time I try to do a 'Clean and Fix' the application crashes (running Win7 x64).

I have reported the problem earlier via bugtracker for version 2.0.0.263 (bug: 213317) and according to bugtracker this bug should be fixed in 2.0.0.964. I am sorry to report, that this is not the case. I still got the same problem (2.0.0.964) and I have not been able to run Clean and Fix not even once.

I have reported this via bugtracker again for the new version with debuglog and bugreport attached.

According to the developer the objective for build 964 is:

1. To bypass the 'Installation problems with certain AV products' in build 963 .

2. Safety improvement: Running the Clean and Fix my computer or File Cleaner with the safest scan option will no longer list any files relating to Windows,

nor any DLL or other executable files.

It is my understanding that hardly any other fixes are imbedded in build 964. See http://www.macecraft.com/news/197/

Well, I am not happy I you are right about this - this means I have to make a new bugreport all over again.

Made some remarks under another topic: http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4089#p25085http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4089#p25085

I really do not see why you should make a new Bugreport all over again! Your reports sent to Bugtracker are not lost or wasted.

aagaard

I really do not see why you should make a new Bugreport all over again! Your reports sent to Bugtracker are not lost or wasted.

Well, I just assumed that if a bug has been booked as fixed in the bug tracker then a developper will have no reason to look at it once again.

Obviously you dont agree - otherwise you would not answer me this way - but to me this is a reasonable assumption.

leonardo

Aagaard wrote
I really do not see why you should make a new Bugreport all over again! Your reports sent to Bugtracker are not lost or wasted.

Well, I just assumed that if a bug has been booked as fixed in the bug tracker then a developper will have no reason to look at it once again.

Obviously you dont agree - otherwise you would not answer me this way - but to me this is a reasonable assumption.

Agreed, the information in Bugtracker is confusing. Stated this way one would assume this is fixed in build 964!

Bug Tracker: Details of bug 213317

Status: Fixed, Fixed version released.

Is this bug fixed in the latest released version? Yes, this bug fix was included to the latest released version of the program.

jv16

Leonardo wrote

Agreed, the information in Bugtracker is confusing. Stated this way one would assume this is fixed in build 964!

Bug Tracker: Details of bug 213317

Status: Fixed, Fixed version released.

Is this bug fixed in the latest released version? Yes, this bug fix was included to the latest released version of the program.

I made changes in order to fix the issue. Since I cannot reproduce the problem, there is also no way for me to verify whether the fix works. That's why I reported the issue as fixed, so the original poster can let me know if the problem still occurs. Which it seems to do.

I didn't want to push out build 964, I'd rather had spent some more time in fixing this issue and a few other random crashes that occur. I'd really like to get these fixed fast, although the problem seems to be quite rare (i.e. happens only on very few systems).

aagaard

I agree that some errors ( i.e. problems with installation) needs to be fixed as first thing.

Rare problems as this one can be hard to fix because you are not able to reproduce it. But looking back at history sometimes might be helpfull.

I.e. this issue was first introduced in version 2.0.0.963, so the problem is probably connected to one or more fixes in that version.

jv16

Aagaard wrote

Rare problems as this one can be hard to fix because you are not able to reproduce it. But looking back at history sometimes might be helpfull.

I.e. this issue was first introduced in version 2.0.0.963, so the problem is probably connected to one or more fixes in that version.

I don't think so. Similar crashes were reported a while, it's pretty random what feature triggers the crash but the BugReport.txt tells me that the problem lies inside the list component.