QBzr

[win32] Subwindows only paint after a keyboard/mouse event.

Bug #632501 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Windows Installers
Fix Released
Critical
Unassigned
QBzr
Invalid
Undecided
Unassigned

Bug Description

bzr.exe 2.2 (official installer) + qbzr 0.19 revno 1312.

I've just observed that running qdiff from qlog is very slow. It takes more time than running qdiff for the same revision from command-line. But I'm not sure what cause this. If I press Enter in qlog on revision then qdiff window shows, there is "Loading..." message in the title and then nothing happens very long time. I've tried to measure this time and didn't touch neither keyboard nor mouse. I have been waiting for 2+ minutes -- nothing happens. Then I've touched the mouse and suddenly qdiff window has been updated.

So, either we have some interesting bug in qbzr, or (more likely) we're bitten by PyQt/Qt again, because bzr 2.2 has newer version of PyQt/Qt bundled.

Tags: win32 pyqt4.7
Revision history for this message
Alexander Belchenko (bialix) wrote :

Gary, do you have any ideas what it could be?

Revision history for this message
Alexander Belchenko (bialix) wrote :

I've downgraded my bzr install to bzr 2.1.2 with Python 2.5 and this problem has disappeared.

Revision history for this message
Alexander Belchenko (bialix) wrote :

Re-installed bzr 2.2: the same problem again. I noticed that I even don't see the throbber. So I guess qdiff window never repainted for some reason.

Going to downgrade to 2.1.2 again.

Revision history for this message
Alexander Belchenko (bialix) wrote :

I mean: So I guess qdiff window never repainted for some reason... until there is some event from mouse/keyboard arrived.

Revision history for this message
Gary van der Merwe (garyvdm) wrote :

It seems to happen with any sub window, including context menus, which makes me agree that it is an qt/pyqt bug.

Changed in qbzr:
status: New → Confirmed
summary: - qdiff invoked from qlog is VERY slow or maybe waiting for some event
+ [win32] Subwindows only paint after a keyboard/mouse event.
Revision history for this message
Gary van der Merwe (garyvdm) wrote :

I think this may be http://bugreports.qt.nokia.com/browse/QTBUG-12721

Revision history for this message
Gary van der Merwe (garyvdm) wrote :

And the version that it is fixed in is not yet released :-( Not sure what to do here.

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 632501] Re: [win32] Subwindows only paint after a keyboard/mouse event.

Gary van der Merwe пишет:
> And the version that it is fixed in is not yet released :-( Not sure
> what to do here.

I have copy of PyQt 4.5.2-1 for Py2.6. I will test whether it's affected
by this bug or not.

--
All the dude wanted was his rug back

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 632501] Re: [win32] Subwindows only paint after a keyboard/mouse event.

Alexander Belchenko пишет:
> Gary van der Merwe пишет:
>> And the version that it is fixed in is not yet released :-( Not sure
>> what to do here.
>
> I have copy of PyQt 4.5.2-1 for Py2.6. I will test whether it's affected
> by this bug or not.

4.5.2 has no problems with this.

Also I should note that with PyQt 4.7 there is also problem with
updating of status view in qlog (list of modified files): sometimes it
does not get updated.

--
All the dude wanted was his rug back

tags: added: pyqt4.7
tags: added: win32
Revision history for this message
Alexander Belchenko (bialix) wrote :

So my proposal: downgrade PyQt to 4.5.2 (or something similar) on build machine and build new bzr.exe installer.

Revision history for this message
Alexander Belchenko (bialix) wrote :

bzr 2.2.1 has PyQt 4.5 inside.

Changed in bzr-windows-installers:
status: New → Fix Released
Changed in qbzr:
status: Confirmed → Invalid
importance: Critical → Undecided
Changed in bzr-windows-installers:
importance: Undecided → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.