[Qt-creator] Qt Creator response too slow

[Matthias Ettrich]

endEditBlock() will emit the cursorPositionChanged()-signals. The position of 
the main cursor is connected to BaseTextEditor::slotCursorPositionChanged(). 
There are also other signals emitted, meaning the problem could lie anywhere.

Please continue profiling using a profiler, we still have no way to reproduce 
any of that :-{

Matthias


On Friday 08 May 2009 12:38:18 pm Ruotsalainen Juha (Nokia-S/Oulu) wrote:
> For anyone interested:
> I added a QTime::start() and elapsed() lines around 'cursor.endEditBlock()'
> in basetexteditor.cpp's line 820 (snapshot downloaded this morning). When I
> experience slow responses in Creator (for my test runs) endEditBlock() at
> that line takes around 1.8 seconds to complete.
>
> Without testing a bit, I would imagine all the sluggishness is due to
> something lengthy happening in endEditBlock(). Quickly looking at the
> endEditBlock() implementation, it is playing around with
> QSharedDataPointer-stuff. That may cause network accesses somewhere in the
> background.
>
> --
> jussi
>
> -----Original Message-----
> From: qt-creator-bounces at trolltech.com
> [mailto:qt-creator-bounces at trolltech.com] On Behalf Of ext Boy Lenssen
> Sent: 07 May, 2009 15:30
> To: qt-creator at trolltech.com
> Subject: Re: [Qt-creator] Qt Creator response too slow
>
> Sounds like you're on the good route! I believe the lasting time (about
> 300 ms) is about what I'm experiencing (or maybe a bit more...not sure)
>
> -----Original Message-----
> From: Juha.Ruotsalainen at nokia.com [mailto:Juha.Ruotsalainen at nokia.com]
> Sent: donderdag 7 mei 2009 13:37
> To: qt-creator at trolltech.com
> Subject: Re: [Qt-creator] Qt Creator response too slow
>
> Valgrind, good as it is, is N/A for Vista.
>
> I did a quick trial runs with Sysinternals' Process Monitor. Test setup
> was the same in both cases: same project, same code file, same point in
> a method, hit enter at that line.
>
> The main difference between 1.0 and 1.1 is that the latter does ends up
> spending 0.3 of a second at the nearest Windows Domain Controller
> (\\xxwdc101\PIPE\samr) doing pipe operations: writing, reading and
> calling
> FileSystemControl (FSCTL_PIPE_TRANSCEIVE). These DC accesses occurred 14
> times in my small log with each occurrence lasting for about 0.2-0.3
> seconds.
>
> You doin' some funky pipe stuff in QtCreator now ;)
>
> --
> jussi
>
>
> -----Original Message-----
> From: qt-creator-bounces at trolltech.com
> [mailto:qt-creator-bounces at trolltech.com] On Behalf Of ext Aleksandar D.
> Balalovski
> Sent: 07 May, 2009 14:19
> To: qt-creator at trolltech.com
> Subject: Re: [Qt-creator] Qt Creator response too slow
>
> On Thu, May 7, 2009 at 1:15 PM,  <Juha.Ruotsalainen at nokia.com> wrote:
> > Is there some option to enable humongous debug/event logs that would
>
> help in pinpointing where time is spent?
>
>
> Maybe with valgrind?