Native 64-bit support.

Forums: 

I think it is time for BleachBit to "grow up" with everyone else and add native 64-bit support. Windows 9 is coming out within a year or so and rumor has it, it won't have a 32-bit version, only 64-bit. 85% - 90% of the population who bought Windows 7 and Windows 8 have 64-bit editions. XP has dropped support and 32-bit is dieing off, so I think a 64-bit version should come out with BleachBit 2.0. I am willing to do whatever testing is needed with my Windows 7 64-bit, when the time comes.

ROCKNROLLKID's picture

Even Linux systems are tackling native 64-bit systems.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

I agree 64-bit native support is a good goal. On Linux, BleachBit 1.3 can already run as a 64-bit process, but on Windows it is mainly a problem of the dependencies. One important dependency is GTK+ where gtk.org labels its support for 64-bit Windows as "experimental," but maybe it's not that bad.

This will be a good thing to consider when updating the old GTK version 2, but one problem with that, on Windows only again, is it will probably make the BleachBit installer much bigger.

---
Andrew, lead developer

ROCKNROLLKID's picture

I guess after 64-bit code is applied, BleachBit size will increase to probably around 9MB, which is quite large for a Cleaner. Maybe you could compress some files in BleachBit, by default to help shrink it, such as CleanerML entries and the lib DLL files could probably stay in a archive format. Maybe some re-write of the code will have to be done, too. I guess you will have to experiment with the code.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

The difference in size of the BleachBit version 1.3 installer between Windows and Linux is about 6.5MB vs 0.5MB because GTK+ and Python (the old versions currently used) take up about 6MB. Newer versions are even bigger.

I have applied various space-saving methods to GTK+ and Python such as deleting files, packing executables and DLLs, and stripping translation files. Work like this can be done for new versions, but it's not trivial work and distracts from other priorities.

You're right: one day Windows will probably not support 32-bit processes, so it will have to be done again.

---
Andrew, lead developer

ROCKNROLLKID's picture

I filed this a BleachBit launchpad as bug #1373564. You can access it here: https://bugs.launchpad.net/bleachbit/+bug/1373564

Hopefully native 64-bit can be done in 2.0 for Windows users.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

So.. here I go reviving a zombie thread with my first comment. The downloader said that it was for the x86 and 64 bit version, but it installed the x86 version. The infernal thing has been deleting windows updates for about 3 hours now. If there is a 4 bit version I want it. Hell, I'd settle for a command line version at this point, this is insane!

Is there a 64 bit version? Win7. If not, I'm afraid that I'm going to have to uninstall and go back to Crap Cleaner.

crogonint: BleachBIt has always had a command-line version.

What advantage do you see to a 64-bit version? The bitness/architecture doesn't affect the speed at which it deletes files.

---
Andrew, lead developer

I thought you needed to use 64 bit to access multiple CPU's with a single process? That thing took like 5 hours to delete 234 MB. I mean come on, throw me a bone?

I don't even have the secure erase thing on.

There is no difference between 32-bit and 64-bit applications in terms of multi-threading and using multiple processors. BleachBit's speed is almost completely determined by the speed of the hard drive, not the CPU. If you look in Windows Task Manager, you'll probably see BleachBit is not using much CPU when it's working because, again, the disk is the bottleneck.

The major advantage of 64-bit applications is they can use access more than 4GB of RAM, but BleachBit doesn't need nearly that much memory.

If BleachBit takes more than five minutes, please see the FAQ: Why does BleachBit take a long time?

---
Andrew, lead developer