Opened 6 years ago
Last modified 3 years ago
#5165 new defect
Weird behaviour of OMEdit when saving
| Reported by: | Francesco Casella | Owned by: | Adeel Asghar |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | OMEdit | Version: | |
| Keywords: | Cc: |
Description
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.
Change History (5)
comment:1 by , 6 years ago
| Milestone: | 1.13.0 → 1.14.0 |
|---|
comment:2 by , 5 years ago
| Milestone: | 1.14.0 → 1.16.0 |
|---|
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0
comment:4 by , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Rescheduled to 1.14.0 after 1.13.0 releasee