Created attachment 490586 [details] Test project for kicad Description of problem: Kicad's pcbnew randomly crashes Xorg. Version-Release number of selected component (if applicable): kicad-2011.01.28-3.rev2765.fc14.x86_64 How reproducible: Very frequent, but not easily reproducible and with no apparent cause (random?). I've seen this happening mostly when editing zone outlines, but also when doing other things. Steps to Reproduce: 1. Open test project (attached) 2. Move the zone outline corners or add corners (right click on the zone outline and select from the menu). 3. Repeat until it crashes. Actual results: It can crash after just two steps, or it can take forever, but it will crash Xorg: Program received signal SIGSEGV, Segmentation fault. 0x00007f50ec8306a7 in fbBresSolid (pDrawable=<value optimized out>, pGC=<value optimized out>, dashOffset=<value optimized out>, signdx=-1, signdy=-4, axis=0, x1=<value optimized out>, y1=0, e=<value optimized out>, e1=6, e3=-8, len=0) at fbseg.c:88 88 WRITE(dst, FbDoMaskRRop (READ(dst), and, xor, bits)); Expected results: It shouldn't crash Xorg ;) Additional info: I'm attaching a test project (this should make it easier for you to reproduce the bug) and a gdb backtrace.
Created attachment 490587 [details] The gdb session with backtrace.
Not trying to be impolite, but I'm using fedora/kicad at work, and this is a very serious and costly problem to me...
I'm using also Fedora and Kicad at work... I didn't succeed to reproduce the bug. Can you make some tries with differents zooms to determine if the zoom value is critical, i.e. no crash if zoom < VALUE and crash if zoom > VALUE or vice versa? How did you get a backtrace if X crashed? It seems to me there is nothing related with kicad in the backtrace you provided.
(In reply to comment #3) > Can you make some tries with differents zooms to determine if the zoom value is > critical, i.e. no crash if zoom < VALUE and crash if zoom > VALUE or vice > versa? I now believe it's no good. See below. > How did you get a backtrace if X crashed? I attached gdb to Xorg, over ssh. > It seems to me there is nothing related with kicad in the backtrace you > provided. True, only the X-side is backtraced. Doing a backtrace on kicad wouldn't be useful, because it would just be killed by X. I'm now convinced that this may not be related kicad, just that kicad is the only app I'm using that triggers it. It's probably a bug with the gfx card drivers. See: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/415357 and https://bugs.freedesktop.org/show_bug.cgi?id=24274 I'm using nouveau with a tricky onboard gpu, so it's possible that the bug is specific to my hardware. I'll investigate further and change the bug component, please allow me some time to do it.
I just tested this at home (I'm using a eeepc), and I managed to easilly reproduce the bug with the attached test-project. This is a standard kicad F14 installation, and the only thing I did was changing the grid to 0.250. After some zoom in/out's, moving/creating zone corners, it happened. I'm definitely ruling out nouveau as the culprit, this must be Xorg itself. Reassigning to Xorg. As a sidenote, I couldn't reproduce the bug with the freedesktop test-app (but then again, neither did the original reporter). I'm going to test with kolourpaint and report back. In the meantime, Alain, could you kindly test this for (say) 1 minute?
I couldn't reproduce the freedesktop wbug with kolourpaint. Moreover, that report was exclusive to intel UXA, which I am at home (Intel 945GME), but not at work (nouveau with EXA there). So I am now assuming this is an unrelated problem. I will now try to find a consistent way of reproducing it.
I believe I'm experiencing this problem as well. I use Linux Mint 12, my X session crashes when using pcbnew (primarily while zooming in and out). I'm using the intel video driver. I've reported the bug here: https://bugs.launchpad.net/kicad/+bug/911963. There are Xorg logs and a gdb backtrace over there as well. If I can do anything to help debug this please let me know.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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