Bug 558095
Summary: | "BadAlloc (insufficient resources for operation)" XError running /usr/share/photofilmstrip/photofilmstrip-gui.py (wxPython/wxWidgets release number mismatch) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stephen Haffly <hafflys> | ||||
Component: | wxPython | Assignee: | Dan Horák <dan> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 12 | CC: | dan, dmalcolm, ivazqueznet, james.antill, jonathansteffan, rpandit | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:876bb74c2f3f09db317cf29545d04c373ffd84ee | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-12-03 23:55:59 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Stephen Haffly
2010-01-23 17:24:50 UTC
Created attachment 386351 [details]
File: backtrace
When I start the program from the command line, this is the message that is displayed: [stephenh@emerald ~]$ photofilmstrip /usr/lib64/python2.6/site-packages/wx-2.8-gtk2-unicode/wx/_core.py:14450: UserWarning: wxPython/wxWidgets release number mismatch warnings.warn("wxPython/wxWidgets release number mismatch") When it crashes, this is the message: Gdk-ERROR **: The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1692127 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Thank you for reporting this bug. I'm not familiar with the "photofilmstrip" application. Do we ship that in Fedora yet? If not, you may want to add it to the wishlist here: https://fedoraproject.org/wiki/Package_maintainers_wishlist (or even package it yourself) How reproducible is this problem? If you run the program from a terminal with the "--sync" option, does the error message change? What is the output of running the following command? rpm -q wxWidgets wxPython Looking at the backtrace, it looks like an XError happened in frame 4 of the program's single thread: BadAlloc (insufficient resources for operation). The "UserWarning: wxPython/wxWidgets release number mismatch" message looks suspicious as well. Reassigning component from "python" to "wxPython"; hopefully the wxPython maintainer will be able to figure this out further or reassign as necessary. This is not a Fedora package, but I hope it becomes one. It gives, in effect, the ability to do what Windows Movie Maker does for putting together a series of photos into a form that can then be burned to DVD. I need it to work with a number of photos that I took while on a trip so that I can pass a copy with narration on to family members. I will add it to the wishlist since I have no idea how to package a program (it does have a DEB installation package, but not an RPM installation package. I installed from source. The problem is reproducible every time. If I run it with photofilmstrip --sync, I get a message the same message: photofilmstrip --sync /usr/lib64/python2.6/site-packages/wx-2.8-gtk2-unicode/wx/_core.py:14450: UserWarning: wxPython/wxWidgets release number mismatch warnings.warn("wxPython/wxWidgets release number mismatch") A window also pops up that says: Invalid PhotoFilmStrip-Project: --sync I just downloaded Photofilmstrip 1.3.3, and the problem still exists with it. I will check the programs website, http://www.photofilmstrip.org/home.html and the sourceforge page, http://sourceforge.net/projects/photostoryx/ for any further information that may help. Stephen, please try to update wxPython package from updates-testing (https://admin.fedoraproject.org/updates/F12/FEDORA-2010-0696). on command line run "yum --enablerepo=updates-testing update wxPython" BTW, how does one add a program to the wishlist? When I go to the link you suggest, it seems it is only for developers, not for end users to request additions. The updated wxPython cleared the error message on the start. I'll know shortly whether it fixed the crash from importing the photos. *** Bug 558837 has been marked as a duplicate of this bug. *** Unfortunately, it aborted again with this message: Gdk-ERROR **: The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1689392 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Aborted (core dumped) I let ABRT submit a bug report, then marked it as a duplicate of this one. (In reply to comment #6) > BTW, how does one add a program to the wishlist? When I go to the link you > suggest, it seems it is only for developers, not for end users to request > additions. I hope we can make that page easier to read; I believe it's intended for end-users as well as developers. I went ahead and added a request for PhotoFilmStrip RPMs for you here: https://fedoraproject.org/wiki/Package_maintainers_wishlist#P Unfortunately I don't expect to be able to package it myself. (the edit is here: https://fedoraproject.org/w/index.php?title=Package_maintainers_wishlist&diff=147863&oldid=147435 ) Thank you for adding this program to the wish list. I have posted all relevant information on the program's bug reporting page as well in the hopes that the developer will figure out what is triggering this fault. Respectfully, Stephen (In reply to comment #11) > Thank you for adding this program to the wish list. I have posted all relevant > information on the program's bug reporting page as well in the hopes that the > developer will figure out what is triggering this fault. Stephen: thanks! If there's a URL for that report can you please post the URL here for reference. This is just a hunch, but one other thing that might be worth trying is to try setting this environment variable when running the program: GDK_NATIVE_WINDOWS=1 photofilmstrip and seeing if this changes the results (it may well not though) (background: some other XError bugs are cropping up in Fedora 12 relating to the switch to client-side windows in gtk-2.18; I believe we're the first distribution to ship 2.18 so we're tending to find the dormant issues with this first; see e.g. this XError issue "in istanbul": bug 543278. See http://library.gnome.org/devel/gtk/stable/gtk-migrating-ClientSideWindows.html for more information) Hope this is helpful Dave Okay, the results were not positive. I did pay attention to the screen and it seemed to be about 7/8 done with loading the pictures (202 photographs) when it abruptly ended. Memory usage was under 1.6 GiB of the 4 GiB installed according to the system monitor with no use of swap space that I could tell (.03 GiB out of 4 GiB) and no change observed while the program was running. I tried a different method. I opened the program and imported 157 pictures. That succeeded. I then went and imported 10 more: success 10 more: success 10 more: success final ones in folder: crash I just received a message from the program's author on Sourceforge's bug reporting page for this program. He stated that the same crash occurs on Ubuntu Karmic 32 bit installation. The crash point is when the number of photographs exceed 200. He also stated that the Windows version loads 500 without problem. Since the problem also manifests itself with an Ubuntu installation, it would indicate that this problem is not Fedora-specific. FWIW, looking further at the backtrace, frame #26 indicates that it's trying to draw the label "100_0817.JPG" in wxDCBase::DrawLabel(), it's calling from there into GDK's text rendering, then into pango, then pango-cairo, and it looks like it can't do it as some resource is exhausted on the X server. My guess is that the program is claiming X server resources (for the images? for the labels?), and that at some point the number of images overwhelms it. That's a hunch though. Hope this is useful. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |