I love this AddOn despite the issues surrounding the freezing... I've noticed certain circumstances when it always freezes... and over time, that as long as I avoid those circumstances, it works well and consistently for me. We play WoW as a family and I maintain all of the computers in our home, so I have used this AddOn on two desktops and two laptops, (all different brands, different levels of performance, two have XP and two have Vista...) ...and the issues seem to occur regardless of the computer/OS...

Thought I'd share my observations--might help other users who just want it to work and/or the author to figure out where the glitch may lie...

1. When I click "Search" and the wtf files are already scrubbed, it freezes. So, if it can't find any Leftover AddOn Settings, it locks up. My practice: I only run CCleaner when I've removed an unwanted addon...

2. Once it freezes, it tends to freeze more frequently. My practice: delete the addon, reload WoW, play for a few seconds, log off WoW, unpack a fresh copy of WoW Crap Cleaner...

3. It seems to not work at all if I hurry to an action just after booting it. My practice: wait a good 5-10 seconds after booting it up.

4. Though having a back-up function is a really smart (essential) option for an addon of this nature, I've noticed that it tends to freeze more frequently after I've run the back-up function and then moved on to the search function. My practice: I don't use the back-up function in the add-on... However, I do manually make copies of my Interface & WTF folders before running it...

5. Though I don't know anything about code or how this works, it seems to me that the problem lies somewhere in telling the addon to do something when it hasn't finished another process or can't find something to do, (whether that be booting up, searching, backing up, deleting settings, scrolling to view the Leftover AddOn Settings or switching tabs...). My practice: handle the add-on like I would a young child... meaning: not rushing it through each task, not asking it to do more than one thing at a time, letting it finish each step before moving on to the next and when it does mess up (aka freeze), wipe the slate clean and give it a fresh start.

So, yes, this AddOn does have issues. But IMHO, the benefits of this little gem FAR outweigh it's idiosyncrasies. As long as I respect those idiosyncrasies, it keeps my files squeaky clean!

I had the same problem with this program until I renamed the Backup folder to something else. Then it worked without any troubles.


Second that. ^

It's safe to assume this program has been abandoned since it hasn't been updated in nearly a year and it is still in beta.

Since it has severe issues, in my opinion, it may be a good idea to stay clear of it.

Working fine for me on Windows 7 x64

Bump

I LOVE this tool. Been using it for a little while, but I recently took a break from the game and when I came back I forgot all about it. I installed a UI mod that comes with a ton of leftover addon settings that I didn't know about. I started getting really weird texture problems, like shimmery transparencies and stuff. I ran this and removed a ton of leftover settings and the problem disappeared. Any ideas why? Either way I'm soooo in love with this lol.

Help anyone????

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '-1' is not valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListBox.ObjectCollection.RemoveAt(Int32 index)
at WoWCrapCleaner.frmMain.Search_WTF()
at WoWCrapCleaner.frmMain.Search()
at WoWCrapCleaner.frmMain.btnSearch_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4216 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WoW Crap Cleaner
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/User/Desktop/WoW%20Crap%20Cleaner.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4215 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4214 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.