id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5165	Weird behaviour of OMEdit when saving	Francesco Casella	Adeel Asghar	"I'm using the latest Windows 64 bit nightly build of OMEdit. Sometimes, when saving models, OMEdit takes a really long time to perform a task which is other times much faster.

What is weird is that the CPU load reported by Windows for the OMEdit task is not 25% (which would mean one out of four virtual cores of my laptop is working full load) but more like 10-12%. The disk load is close to zero. It is as if the OMEdit process is waiting for some input, but if it not the disk, what could it be? I understand time spent waiting for cache misses response is reported by Windows as busy CPU, so it can't be that.

Restarting OMEdit usually (but not always) solves the problem.

I understand this is quite difficult to reproduce, but maybe others have observed this behaviour, or you may have an idea of what is causing it."	defect	new	high		OMEdit