Submitted by Jon on 2011/02/27 09:44
 Using version K.
 
1. I select a TLI with 80 or so children. The child items also have a couple of subs.
2. Select map view.
3. Usually this is sufficient to freeze IQ. If the map view displays successfully, close it and try displaying it again.
 
I usually experience a freeze on the first attempt, but always during the second try.

 
Jon

Comments

I haven't been able to reproduce it yet, but I'll try again later today.

Jon

2011/02/28 14:11

Permalink

Thank you Armando, I appreciate it. For your information, this happens on all off my computers. One has 2GB RAM, the others have 4GB. Running XP SP3, Vista Business, and Windows 7.
 
Jon 

Armando

2011/02/28 16:15

Permalink

Here's what I noticed : the map view is very CPU intensive. When I have many items displayed, scrolling up/down is very choppy and CPU is at 100%. When there are over 80 items in there, IQ is constantly at 100%. Anybody else ?

Jon

2011/02/28 17:13

Permalink

Yes, that is right. However it generally freezes IQ the first time I try it during a session. The second time is guaranteed to make IQ comatose.
 
Jon 

Strange, on my 7 year old notebook, a TLI with 120 sub-items takes < 10 seconds to open.
 
Can you try to do it on another TLI ?
 
To find such items, set a grid source to: nbChildren >50
 

Jon

2011/03/08 07:37

Permalink

This happens with all databases when I follow the steps I described. Armando described something similar and noted that the CPU usage was high. This is true for me as well. Perhaps I am not giving IQ enough time to complete the process, although I have let it try for five minutes before I killed it. That is excessive. All of my tests are with machines with adequate configurations. The minimum configuration is XP SP3, 4GB  RAM, 1TB hard drive, Pentium Dual Core 2.70 GHz. 
 
Jon

Armando

2011/03/08 10:47

Permalink

Yes it happens here too, as I said. With about 150 items in the map view, scrolling is difficult, and CPU stays high all the time. Closing the map view clears things up. Now, it could be because of conditional formatting or item Color, or nbchildren in general. I haven't done many tests.

Confirmed and fixed in v0.9.25L
 
Also in v0.9.25L: Ctrl+Wheel: Zoom in / Zoom out
 

Armando

2011/03/14 17:47

Permalink

[quote=Pierre_Admin]
Confirmed and fixed in v0.9.25L
 
Also in v0.9.25L: Ctrl+Wheel: Zoom in / Zoom out
 
[/quote] Nice.

Jon

2011/03/17 04:38

Permalink

Thank you. This seems to be working well.
 
Jon