PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 191 - Problem with destroying widgets
: Problem with destroying widgets
Status: CLOSED INVALID
Product: PySide
Classification: Unclassified
Component: PySide
: HEAD
: All All
: P5 normal
Assigned To: renato filho
:
:
:
  Show dependency treegraph
 
Reported: 2010-03-23 10:09 EET by zaiceva
Modified: 2010-08-13 11:26 EEST (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zaiceva 2010-03-23 10:09:04 EET
Our application uses Pyside for GUI, and we have some problem with destroying
 widgets. Describing bug:
1) start version scribo with Pyside(for example, scribo v0.2.2 - commit 212),
and let we have one account with loading posts.
2) we go to the window for adding post or viewing posts on click at the
corresponding button.
3) close application(we click on "exit" button on menu or on the top-right
corner)
4) in console:
$ ./scribo.py 
./ldm/Account.py:52: DeprecationWarning: object.__new__() takes no parameters
  return super(Account, cls).__new__(cls, id)
<LivejAccount.LivejAccount object at 0x918e16c>
1
51
Segmentation fault

Also we would have this error, if we try to destroy Pyside widgets directly in
code(with using "deleteLater" method).
For example:
widg = self.stack_widg.currentWidget()
self.stack_widg.removeWidget(widg)
widg.deleteLater()

(this example in part of code, responsible for going to previous window,
stack_widg has type QStackedLayout, and has a parent central widget, which is
in main window)
So, segmentation fault is in case, when we try to destroy widgets directly or
closing our application.
Comment 1 Hugo Parente Lima 2010-03-24 18:51:55 EET
What PySide version? 0.2.2 (boost based) or 0.3.0 (shiboken based) ?
Comment 2 zaiceva 2010-03-25 07:11:17 EET
we use package:
python-pyside version: 0.2.3-9.1
Comment 3 Hugo Parente Lima 2010-04-08 18:53:36 EEST
Could you test with 0.3.0 packages?
Comment 4 zaiceva 2010-04-10 07:04:04 EEST
No, we don't test on 0.3.0 version because we don't have this version in
repository. We would have attempt to start our application on 0.3.0 pyside
version, if we don't have problem with install packages pyside(version 0.3.0)
from maemo.org, but we don't promise to do it soon.
Comment 5 renato filho 2010-05-21 09:45:23 EEST
Tested with Scribo 0.2.10 and PySide version 0.3.1 and works fine.

PySide 0.3.1 is available on extra devel repository. Cold you try this?
Comment 6 zaiceva 2010-05-25 05:30:08 EEST
Comment from our testing team:

We found two various SIGSEGV:

    * at 0xABCF3B2: QRasterWindowSurface::~QRasterWindowSurface() (in
/targets/FREMANTLE_X86/opt/lib/libQtGui.so.4.6.2)
          o This problem was fixed in PySide 0.3.1. Thanks. 
    * at 0x80BC3A9: PyErr_Fetch (in /targets/FREMANTLE_X86/usr/bin/python2.5)
          o It was problem in our malformed code (trying delete object in class
destructor, when object already deleted)