View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004989 | MMW v4 | Install/Config | public | 2008-12-02 14:31 | 2013-11-06 15:25 |
Reporter | Ludek | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | unable to reproduce | ||
Product Version | 4.1 | ||||
Summary | 0004989: Initialization of 'Options' dialog is slow | ||||
Description | It takes to me more than 5 seconds to initialize 'Options' dialog. I have added debug messages so that we could review what could be done faster. | ||||
Tags | No tags attached. | ||||
Fixed in build | 1199 | ||||
|
The debug messages added in build 1199. |
|
I am not sure what was causing this. My system was somehow stuck probably. Now, I have no issues with this. Options dialog is shown in 2 seconds. |
|
Verified 1201. Options dialog loads in ~1.5 seconds |
|
I'm experiencing this in MMW 4.1. Debug logs uploaded. Problem can be seen in the logs at: Clicked Options . . . . . . . Dialog appeared 0000180:0001398 . . . . . . . . . . . . 1477 1507 . . . . . . . . . . . . . 1563 1804 . . . . . . . . . . . . . . 1885 (this is the best example) |
|
I see from the log that initialization of the options dialog takes 1 - 1.5 seconds, the rest is showing of the form. You indicated over IM that skinless version takes 1.5 - 2 seconds while skinned takes more than 5 seconds to show, so it looks like a skinning/rendering issue. Could you confirm that you see the same with 4.0.7 so that we know whether it is regression or not? I am going to perform some tests on an older computer to see if I can replicate. EDIT: I cannot replicate with any of my machines/OS. Even on my oldest computer the Options dialog is shown in less than 1 second and init. takes just 0.1 second. Couldn't it be related to graphic card drivers upgrade or any configuration change on your computer recently? I guess you cannot replicate it with another machine, right? Which OS you are running? |
|
I'm unable to consistently reproduce this issue. But I did verify that performance is roughly the same for both 4.0.7 and 4.1. |