Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Hi there. We unknowingly push files like java_pid1067.hprof from AndroidStudio at runtime. We delete

Data detected by BFG cleaner:

PS C:\Users\alish\StudioProjects\mytaxi-room> java -jar bfg-1.14.0.jar --strip-blobs-bigger-than 20M .

Using repo : C:\Users\alish\StudioProjects\mytaxi-room\.\.git

Scanning packfile for large blobs: 47086
Scanning packfile for large blobs completed in 479 ms.
Found 7 blob ids for large blobs - biggest=2554436571 smallest=2191147420
Total size (unpacked)=17118745411
Found 1954 objects to protect
Found 74 commit-pointing refs : HEAD, refs/heads/feature/room_migration, refs/heads/master, ...
Found 1 tag-pointing refs : refs/tags/'v3.3.13'

Protected commits

These are your protected commits, and so their contents will NOT be altered:

* commit f0a5c901 (protected by 'HEAD')


Found 1710 commits
Cleaning commits: 100% (1710/1710)
Cleaning commits completed in 1 725 ms.

Updating 6 Refs

Ref Before After
refs/heads/feature/room_migration | f0a5c901 | e65685cc
refs/heads/test | f0a5c901 | e65685cc
refs/remotes/origin/feature/mapbox-10 | 850a9cf0 | 0d6061f8
refs/remotes/origin/feature/room_migration | f0a5c901 | e65685cc
refs/remotes/origin/feature/single_activity | e372e724 | f2eff801
refs/remotes/origin/feature/single_activity_mapbox | 18550070 | ba70b4b0

Updating references: 100% (6/6)
...Ref update completed in 107 ms.

Commit Tree-Dirt History

Earliest Latest
| |

D = dirty commits (file tree fixed)
m = modified commits (commit message or parents changed)
. = clean commits (no changes to file tree)

Before After
First modified commit | de5967fb | 7f9ba842
Last dirty commit | 8a207018 | ad1644e1

Deleted files

Filename Git id
java_pid1067.hprof | a50a77ac (2,0 GB)
java_pid13233.hprof | d156683e (2,3 GB)
java_pid4488.hprof | 2e97d2fd (2,2 GB)
java_pid8304.hprof | eb6c9e7d (2,3 GB)
java_pid9024.hprof | e0ad631a (2,4 GB)
java_pid9436.hprof | e5257193 (2,3 GB)
java_pid9773.hprof | 2c750689 (2,3 GB)

In total, 236 object ids were changed. Full details are logged here:


BFG run is complete! When ready, run: git reflog expire --expire=now --all && git gc --prune=now --aggressi

1 answer

1 accepted

1 vote
Answer accepted

Hi @Alisher Qazaqbaev and welcome to the community.

I assume that you would like a garbage collection for the repo where you accidentally pushed a large file and that you have cleaned with BFG?

I checked in our system the repos your account has access to and I could see one repo with a size of 4GB. I assume that is the repo with the large file?

I ran a git gc for this repo and its size is 60.6 MB now.

Please feel free to let me know if it looks ok, if you are able to push now, and if you need anything further.

Just a heads up, since that repo belongs on a workspace on a paid billing plan, you can also raise a ticket with the support team in the future if you ever need assistance with that repo, to ensure a faster response. You can create a ticket via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Kind regards,

Thanks to the Atlassian Team for your help! We are very happy that this issue has been resolved

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,494 views 3 10
Read article

Atlassian Community Events