[master] Refresh action can cause segmentation fault or freeze, and often very slow

Bug #395175 reported by Alexey Balmashnov
62
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Bazaar Explorer
Confirmed
High
Unassigned

Bug Description

bzr-explorer 0.4

To reproduce:
1. Run explorer
2. Run refresh to be performed

Second attempt causes "Segmentation fault".

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 395175] [NEW] Refresh twice in a row causes segmentation fault

Alexey Balmashnov пишет:
> Public bug reported:
>
> bzr-explorer 0.4
>
> To reproduce:
> 1. Run explorer
> 2. Run refresh to be performed
>
> Second attempt causes "Segmentation fault".

What is your PyQt version, OS, bzr version?

Revision history for this message
Alexey Balmashnov (a.balmashnov) wrote : Re: Refresh twice in a row causes segmentation fault

Package: python-qt4
Version: 4.4.4-2ubuntu6

Ubuntu 9.04

$ bzr --version
Bazaar (bzr) 1.16.1
  Python interpreter: /usr/bin/python 2.6.2
  Python standard library: /usr/lib/python2.6
  bzrlib: /usr/lib/python2.6/dist-packages/bzrlib

Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

This is really ugly. I'm seeing the same thing occasionally. I'm yet to go digging but it seems like refreshing the status report multiple times is ok but it segfaults if the repo view (or welcome page?) has been refreshed previously. Or something like that.

Changed in bzr-explorer:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Gary van der Merwe (garyvdm) wrote :

Some tips to solve this:
* Use the modeltest.py from PyQt. Try reproduce the refresh that is happening that is causing the segfault while model test is connected to the model. Qbzr has a class to make modeltest operate better in conjunction with bzr's test suit (see /lib/test/excepthookwatcher.py from qbzr).

* See this change: http://bazaar.launchpad.net/~garyvdm/qbzr/commitstuff/revision/831.1.5 The symptoms were similar.

Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote : Re: Refresh action can cause segmentation fault or freeze

Some users are reporting freezes on Windows 7 for this problem.

summary: - Refresh twice in a row causes segmentation fault
+ Refresh action can cause segmentation fault or freeze
Revision history for this message
Luis Arias (kaaloo) wrote :

I'm regularly experiencing refresh related segmentation faults on 64-bit karmic. I don't see how to provide more information as there is nothing in the logs. Please let me know if there is something I can try.

Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

Rev 467 of the 1.0 branch has some code which may reduce the frequency of this occurring. Please test.

Revision history for this message
Luis Arias (kaaloo) wrote : Re: [Bug 395175] Re: Refresh action can cause segmentation fault or freeze

Thanks Ian !

I will be testing and post here !

Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote : Re: Refresh action can cause segmentation fault or freeze

The frequency of this problem has definitely dropped a lot for me. Just happened again though after reverting a merge.

Revision history for this message
dmuir (dmuir) wrote :

Is this something that has improved with newer versions of Ubuntu?

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 395175] Re: Refresh action can cause segmentation fault or freeze

dmuir пишет:
> Is this something that has improved with newer versions of Ubuntu?

Yes, it should be better, though not always :-/

tags: added: mvp
Revision history for this message
Alexander Belchenko (bialix) wrote : Re: Refresh action can cause segmentation fault or freeze

Partially fixed in trunk, please test and say if it's better now.

tags: added: feel-faster multiprocess performance
tags: added: refresh
summary: - Refresh action can cause segmentation fault or freeze
+ [master] Refresh action can cause segmentation fault or freeze, and
+ often very slow
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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