I’m using Kicad 4.0.4-stable, release build
with wxWidgets 3.0.2 Unicode and Boost 1.57.0
on a Win7 SP1 64 Bit (it would be nice it this info could be copied )
I’ve been working in a board for a couple of day, so far without and issued, now, when trying to optimize my layout Kicad is crashing when filling the copper zones up, so far I have been able to reproduce the error, but I’ve not been able to fine any log files or crash dump to post here.
In the firs picture the filled zones work as expected as seen in the screenshot:
But in third picture, when pressing trying to fill up the zones Kicad crashes, notice that I haven’t even connect the bypass capacitor yet, just vias to the pads
The boards has other components and some of them are already partially routed, unfortunatly, I’m not sure where exactly the problem is coming from, just that it is triggered when I’m trying to route this component.
I hope somebody can take a look, I will try to help as much as I can.
I have also seen some odd behavior with KiCad crashing when I hit ‘B’.
This seems to only happen when my gamer instincts take over and I hit ‘B’ repeatedly…
…but when it does happen, all KiCad windows will immediately close.
If you guys can replicate the bug, hit the buglist with it.
Dev’s frequent KiCAD.info from time to time, but won’t track bugs reported here - that’s what they have the buglist for:
@der.ule [quote=“der.ule, post:1, topic:4120”]
it would be nice it this info could be copied
[/quote]
KiCAD main window > Help > About KiCAD … [Copy Version Info] button at bottom/right.
Thanks, I will do that, also, when my board is finished, I will go back and test it with 4.0.4, other issues have arise with the nightly version that I will report.
If the bug is in the ‘stable’ release then it should be reported. It’s good to hear it doesn’t happen in the development branch, but someone will have to take time to reproduce it and port the fix to the ‘stable’ branch.
This whole release elasticity around KiCad seems a little strange to me ?
There is a “stable-release”, which is often less stable than the developments, and fixes seem to not have a defined trajectory to new “stable” releases, from developments.
I’m more used to having any fix in development, having a simple delayed-path to the next stable release.
The stable release will generally not have any new features (unless the feature is trivial). Since the development branch has so many new features, any fix to an existing problem has to be carefully checked and applied to the stable branch. The bug was likely always in the stable branch but not enough people were tripping it and it went unreported. There was some work done on the polygon code since then and something in there might have fixed the bug. I doubt the dev branch has fewer bugs; there are so many new features there are no doubt many still undiscovered bugs.
Thanks for the response, I agree, I have some issues with the nightly, but at least the are no killers, I can continue working and if it freezes sometimes or I’m forced to work in the non-opengl mode, I can live with that. But if it doen’t work at all, then I have a problem. I’ll go to the tracker and fill up a bug report (if none existing).
)
