Last month, we upgraded to Crucible 3.2.3, and started noticing a memory leak issue with the tool. The leak seems to be associated with Fisheye scanning a large repository. The leak causes the server to restart - we have the default panic_on_oom turned on. The large repo in question did not index to completion with previous versions of crucible. The indexing would stop midway or error out without completion.

Have you noticed anything similar? Any tips on how to avoid the issue.

1 answer


It is not possible to determine exactly how much memory Crucible needs, as this would depend of things like size and complexity of repositories and its indexing operations, for example, so large and complex repositories will require sometimes a large amount of memory.

As you said this repository never got indexed, it seems it needs indeed more memory for it. The following document may be helpful in your case, as it points how to increase the memory available:

Attend to increase the -Xmx value, which is the maximum memory allowed for your Crucible instance.

You may also find valuable information in the following documents regarding the configuration of FishEye in order to get a better performance while indexing:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

56 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you