Modelio 3 - Issue #165 element view bug

Transcription

1 Modelio 3 - Issue #165 element view bug 06 January :19 - Robin Zhang Status: Closed Start date: 06 January 2014 Priority: Urgent Due date: Assignee: Christophe Malgouyres % Done: 100% Category: Estimated time: 0.00 hour Target version: Modelio Description within modelio3.1, created a class in class diagram, it will be waite a long time after clicked the element view. Related issues: Related to Issue # 169: element view problem Closed 07 January 2014 Related to Issue # 180: Modelio freezes when Element Tab is open Closed 20 February 2014 History #1-06 January :04 - Matthieu Bachelier I have the same problem too. It should be in higher priority: it s almost unusable. #2-07 January :24 - Cédric Marin Hello, I can t reproduce the problem here.what I did : 1. open a project 2. create a class diagram 3. choose the create a class tool 4. click in the diagram ==> a class is created immediately 5. click on the class 6. click on the Element tab to display the element properties ==> the properties are displayed immediately. Can you detail the steps to reproduce the issue? Can you tell us your machine specs (CPU, RAM ) and your operating system (Windows/Linux 32/64bits )? In order to help us fixing the problem you may also: 1. Go to the Configuration/Preferences menu, 2. In the Administration tab, choose Debug Log level, 3. Reproduce the problem, 4. Go to the Help/Open log file menu, 5. Send the log content as an attached file Thanks for the help! #3-09 January :00 - Matthieu Bachelier - File log_file.txt added 08 May /8

2 Cédric Marin wrote: Hello, I can t reproduce the problem here.what I did : 1. open a project 2. create a class diagram 3. choose the create a class tool 4. click in the diagram ==> a class is created immediately 5. click on the class 6. click on the Element tab to display the element properties ==> the properties are displayed immediately. Can you detail the steps to reproduce the issue? Can you tell us your machine specs (CPU, RAM ) and your operating system (Windows/Linux 32/64bits )? In order to help us fixing the problem you may also: 1. Go to the Configuration/Preferences menu, 2. In the Administration tab, choose Debug Log level, 3. Reproduce the problem, 4. Go to the Help/Open log file menu, 5. Send the log content as an attached file Thanks for the help! The steps to reproduce the bug are correct. It takes almost 1 minute to display properties! And each time I interact with something, it takes another minute if the selected view is Element view :( In attachement, you ll find a debug file. But it doesn t contain any DEBUG terms (it seems). My workstations are : Windows 7 32-bits (Intel Pentium G630, 4GB) and Windows bits (Intel Core i37xx, 8GB). #4-10 January :39 - Cédric Marin The log effectively contains nothing useful. There is another way to help us but it will require you to have the Oracle JDK 1.7 installed: 1. First get if you don t have it the Oracle JDK 1.7 (older may not work). You can find it here 2. In the jdk/bin directory you will find a jvisualvm tool, run it and close the start page tab. 3. Run Modelio ==> In JVisualVM browser, the Modelio process will appear. 4. In JVisualVM browser, double click on the Modelio process. 08 May /8

3 ==> Modelio is now attached to JVisualVM. 5. Select the Threads tab. 6. In Modelio, reproduce the problem. 7. While Modelio is stuck/busy/frozen/, go to JVisualVM and click on Thread dump button 3 times, waiting a few seconds between each click. ==> 3 new tabs will open with all threads stack trace. 8. Send us these tabs content as attached files. 9. You may also try the Sampler which displays where in the code CPU spends its time. Thanks for the help! #5-11 January :39 - Matthieu Bachelier - File dump.zip added Cédric Marin wrote: The log effectively contains nothing useful. There is another way to help us but it will require you to have the Oracle JDK 1.7 installed: 1. First get if you don t have it the Oracle JDK 1.7 (older may not work). You can find it here 2. In the jdk/bin directory you will find a jvisualvm tool, run it and close the start page tab. 3. Run Modelio ==> In JVisualVM browser, the Modelio process will appear. 4. In JVisualVM browser, double click on the Modelio process. ==> Modelio is now attached to JVisualVM. 5. Select the Threads tab. 6. In Modelio, reproduce the problem. 08 May /8

4 7. While Modelio is stuck/busy/frozen/, go to JVisualVM and click on Thread dump button 3 times, waiting a few seconds between each click. ==> 3 new tabs will open with all threads stack trace. 8. Send us these tabs content as attached files. 9. You may also try the Sampler which displays where in the code CPU spends its time. Thanks for the help! You ll find requested files in attachement! #6-20 January :16 - Cédric Marin Hello, The bug is related to a third party library (ktable) and could occur only on Windows. It may be caused by one displayed property being very long (much more than 100 characters). As a workaround, check the name and all properties of your elements. By example if you use the Java module, check attributes initial values. #7-20 January :30 - Cédric Marin I created an issue on the ktable forge: #8-11 March :06 - András Lukács This is irritating, indeed. Slows down modelling so much that one is considering dumping Modelio altogether. When I select a model element or the background, and the Element tab is visible, 90% of the times it takes ca. 5 seconds for the user interface to be usable again. In the meantime, the horizontal scroll bar of the right-hand section of the Element tab (this is where you can set the active element s properties) is rapidly being resized several times. I don t mean to be smarter than the guys who maintain Modelio but isn t there some BeginUpdate() / EndUpdate() functionality in ktable they could use when modifying the contents of the window so it should not want to display itself after every single change? #9-17 March :40 - Christophe Demeulemeester - Status changed from New to Assigned - Assignee set to Christophe Demeulemeester - Priority changed from Medium to Urgent #10-02 April :26 - Christophe Demeulemeester 08 May /8

5 This issue has been reported by several users, but we have been unable to reproduce it here, although we ve tested it on several workstations with different OS: Windows 8.1 (x86_64) Windows 7 SP1 (x86/x86_64) Redhat Enterprise Linux 6 (x86/x86_64) Ubuntu Linux LTS (i386/amd64) Debian 6 (i386/amd64) Mac OS X Mac OS X Users who reproduce it only use a very simple model, just a single Class in a Class Diagram, with no special properties Reproduced by Matthieu Bachelier: Start any project under Windows 7 or Windows 8. It will freeze with one class in the class diagram. No need to have a specific project. Reproduced by András Lukács: I mainly use Modelio on two notebook computers. Both run Windows 7 Home Premium 64 bit, and are always updated by the latest Windows and Microsoft updates. I can only give a hardware specification of one of them right now: Windows Home Premium 64 bit (6.1, build 7601) Toshiba Satellite L670 CPU: i3 2.53GHz memory: 4 GB video card: ATI Mobility Radeon HD 5470 main video drivers: atiu9p64.dll, aticfx64.dll, version ; DDI version: 11; WDM 1.1 DirectX 11 screen resolution: 1600 x 900, 32 bit (although I guess this won't matter much) sound card: Realtek High Definition Audio sound card driver: RTKVHD64.sys; version Reproduced by Francesco Maria Cultrera: OS Name: Microsoft Windows 8.1 OS Version: N/A Build 9600 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free System Manufacturer: Sony Corporation System Model: SVS15112C5E System Type: x64-based PC Processor(s): 1 Processor(s) Installed. [01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~2200 Mhz BIOS Version: Insyde Corp. R1021C8, 3/13/2013 Windows Directory: C:\WINDOWS System Directory: C:\WINDOWS\system32 Boot Device: \Device\HarddiskVolume3 System Locale: it;italian (Italy) Input Locale: it;italian (Italy) 08 May /8

6 Time Zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna Total Physical Memory: 12,167 MB Available Physical Memory: 9,499 MB Virtual Memory: Max Size: 14,023 MB Virtual Memory: Available: 11,303 MB Virtual Memory: In Use: 2,720 MB Page File Location(s): C:\pagefile.sys Hotfix(s): 56 Hotfix(s) Installed. [01]: KB _Microsoft-Windows-CameraCodec-Package [02]: KB [03]: KB [04]: KB [05]: KB [06]: KB [07]: KB [08]: KB [09]: KB [10]: KB [11]: KB [12]: KB [13]: KB [14]: KB [15]: KB [16]: KB [17]: KB [18]: KB [19]: KB [20]: KB [21]: KB [22]: KB [23]: KB [24]: KB [25]: KB [26]: KB [27]: KB [28]: KB [29]: KB [30]: KB [31]: KB [32]: KB [33]: KB [34]: KB [35]: KB [36]: KB [37]: KB [38]: KB [39]: KB [40]: KB [41]: KB [42]: KB [43]: KB [44]: KB [45]: KB May /8

7 [46]: KB [47]: KB [48]: KB [49]: KB [50]: KB [51]: KB [52]: KB [53]: KB [54]: KB [55]: KB [56]: KB Network Card(s): 3 NIC(s) Installed. [01]: Controller Realtek PCIe GBE Family Connection Name: Ethernet [02]: Intel(R) Centrino(R) Advanced-N 6235 Connection Name: Wi-Fi Status: Media disconnected [03]: VirtualBox Host-Only Ethernet Adapter Connection Name: VirtualBox Host-Only Network DHCP Enabled: No Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: Yes Second Level Address Translation: Yes Data Execution Prevention Available: Yes #11-06 May :21 - Chris Hoogeboom András Lukács wrote: This is irritating, indeed. Slows down modelling so much that one is considering dumping Modelio altogether. When I select a model element or the background, and the Element tab is visible, 90% of the times it takes ca. 5 seconds for the user interface to be usable again. In the meantime, the horizontal scroll bar of the right-hand section of the Element tab (this is where you can set the active element s properties) is rapidly being resized several times. I am also experiencing exactly this problem. I have a brand new project with only a few elements. Please let me know if there is any more information that would help you fix this bug! OS Name: Microsoft Windows 7 Professional OS Version: Service Pack 1 Build 7601 OS Manufacturer: Microsoft Corporation OS Configuration: Member Workstation OS Build Type: Multiprocessor Free System Manufacturer: Dell Inc. System Model: Precision M6600 System Type: x64-based PC Processor(s): 1 Processor(s) Installed. [01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2401 Mhz BIOS Version: Dell Inc. A12, 8/9/2012 Total Physical Memory: 16,341 MB Available Physical Memory: 10,857 MB 08 May /8

8 Virtual Memory: Max Size: 32,680 MB Virtual Memory: Available: 25,709 MB Virtual Memory: In Use: 6,971 MB Edit: I experience this problem in both Modelio 3.0 and Modelio 3.1.1, but not in Modelio #12-16 May :21 - Christophe Demeulemeester Possible workaround :Switch the Element view to Vertical Layout #13-19 May :42 - Christophe Malgouyres - Status changed from Assigned to Resolved - Target version set to Modelio % Done changed from 0 to 50 This problems came from KTable refreshing its scrollbars a lot more often than necessary Fixed in Modelio #14-19 May :49 - Christophe Malgouyres - Assignee changed from Christophe Demeulemeester to Christophe Malgouyres #15-20 May :46 - Christophe Demeulemeester - Target version deleted (Modelio 3.1.2) #16-20 May :03 - Christophe Demeulemeester - Status changed from Resolved to Closed - Target version set to Modelio % Done changed from 50 to 100 #17-20 May :17 - Chris Hoogeboom I am still experiencing this problem in Modelio Edit: Nevermind. I was using the wrong version. #18-21 May :16 - Christophe Demeulemeester Validated with Modelio bit on Windows 7 SP1 64-bit. Files log_file.txt 26.3 KB 09 January 2014 Matthieu Bachelier dump.zip 28.6 KB 11 January 2014 Matthieu Bachelier 08 May /8

9