CareerCup

possible causes

1. there may be a log statement in a tight inner loop, and the log category enabled.
2. printing stack trace in a tight loop.
3. something went wrong with coding and entered into infinite loop
etc.

This could be an issue of an exception coming within a loop.

This might due to system out println statement or due to log level is debug .log level should be error in production environment

It might be possible that you have a background thread which could be performing some operation that is failing and there might be retry block which is repeatedly failing and continuous logging. It might be possible that there is verbose logging enabled. It might be possible there is a tight loop that is logging in the background.

It is not clear on what is the purpose of this question ?

It is unclear on the purpose of this question. What are they trying to judge by this question?

There could be multiple reasons on why the log could be getting filled. It might be verbose logging level or exception in a tight loop or a background operation failing continuously and logging.

there could be multiple reason
1) thread are getting exception very time
2) thread are falling because of some internal issue
3) retrying is happening again again
4)it might be possible infinite loop running at background