Blank files in Crucible code review even though revision in Fisheye shows code

Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Blank files in code review even though revision in Fisheye shows code.

Cause

There was a bug for Fisheye/Crucible that was fixed in version 2.7.9. The bug itself was fixed but bad patch files weren't cleaned up as part of the bug fix. For reference:

CRUC-6013 - If during review creation the content of a file revision can't be uploaded (via FishEye), that file is regarded as having no content

Resolution

If currently running a version prior to 2.7.9 proceed by upgrading to the latest version. Otherwise, remove current diff index files to trigger Crucible to re-fetch the diff information the next time the review is accessed.

  1. Go to FISHEYE_INST/var/data/uploads. Note the nested directory/file structure, e.g. 00/00/1.dat.

  2. Backup the directory.

  3. Delete all zero length files from the uploads directory. For example, if using Unix, this can be done with the following command:

    find . -type f -size 0 | xargs rm
Updated on September 25, 2025

Still need help?

The Atlassian Community is here for you.