id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5681	huge amounts of logging data	john.pye@…	somebody	"Hi there

Simon was working on a big model at CEA-LITEN and found that he was getting crashes (out of memory) from OMEdit. It turned out that he was logging a huge amount of data into the log window, and that was filling up the memory.

I would suggest that this issue could be resolved by using a buffer in this window, instead of an endless string. The buffer could just store the last N lines. This would avoid out of memory errors, and could be user-configurable to allow more or less lines of buffer as desired.

One must ask the question why people leave logging turned on for long-running simulations. It is so that they have some information visible if (when) the simulation finally fails. The leads to another possible solution for this issue, which would be to find ways to provide the logging/reporting/inspection of the model and/or solver state after the solver fails. Currently there doesn't seem to be any way to do that, hence users just output lots and lots of data and comb through it only for the tiny last bit of the output which actually matters to them. It's all a little bit inefficient as an approach, and could perhaps be tackled in some future work, in some way.

I wasn't sure which component to report this to, so left it *unknown*.

Cheers
JP"	enhancement	closed	high	1.14.0	OMEdit		duplicate