kicad-developers team mailing list archive

[Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>]

… no need for a patch anymore.
Jean-Pierre just removed the code with rev. 5648.

Would be interesting if Andy still can reproduce with a new daily tomorrow…


Regards,
Bernhard


> On 08.05.2015, at 17:13, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> I can also quickly throw together a new debug build on my server if someone has a link to the patch whenever it comes out.  A lot of the work I did while setting up the nightlies was enabling things like this, so I can quickly make new builds in a parallel track before changing "mainline".
> 
> Adam Wolf
> 
> On Fri, May 8, 2015 at 9:59 AM, <devel@xxxxxxxxx <mailto:devel@xxxxxxxxx>> wrote:
> > Hi Andy,
> >
> > can you reproduce the new one with your own builds?
> > If yes, I could provide a small patch tomorrow just to try some thing to
> > verify if it is related to the wxClientDC from the old wxWidgets ticket I
> > posted.
> 
> Yes, it does happen on my own builds. When you get your patch together I
> will try it!
> 
> 
> 
> > If you want to try yourself, you could remove/comment  in
> >   pcbnew/onrightclick.cpp
> > the line 63
> >   wxClientDC  dc( m_canvas );
> > and all
> >   m_canvas->CrossHairOff( &dc );
> > resp.
> >   m_canvas->CrossHairOn( &dc );
> > in lines 79, 133, 492 (and maybe more I missed in between).
> > Might cause issues with the cursor, but just to find out if the wxCLientDC
> > is the culprit...
> >
> > I will also try if I can reproduce.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 08 May 2015, at 05:22, Andy Peters <devel@xxxxxxxxx <mailto:devel@xxxxxxxxx>> wrote:
> >>
> >>
> >>> On May 6, 2015, at 12:55 PM, Andy Peters <devel@xxxxxxxxx <mailto:devel@xxxxxxxxx>> wrote:
> >>>
> >>> Using Adam’s nightly OS X builds, most recently BZR 5645, pcbnew is
> >>> repeatedly crashing. It happens on both my 10.9 machine and my 10.10
> >>> machine. In OpenGL mode, it seems to get confused about menus, or
> >>> something. It happens if I right-click to do something. I am not
> >>> exactly sure what conditions cause it. Attached is the relevant part of
> >>> the bug report:
> >>>
> >>>
> >>> Crashed Thread:        0  Dispatch queue: com.apple.main-thread
> >>>
> >>> Exception Type:        EXC_CRASH (SIGABRT)
> >>> Exception Codes:       0x0000000000000000, 0x0000000000000000
> >>>
> >>> Application Specific Information:
> >>> *** Terminating app due to uncaught exception
> >>> 'NSInternalInconsistencyException', reason: 'Menu to be set as submenu
> >>> is already a submenu of some menu.'
> >>> abort() called
> >>> terminating with uncaught exception of type NSException
> >>
> >> OK, some more testing. I built BZR 5645 on the 10.9 machine.
> >>
> >> As Bob has noticed, it can sometimes be difficult to select a thin line,
> >> such as the board outline on the edge cuts. You have to be pretty
> >> accurate with your mouse. And I’ve noticed that if I just
> >> click-click-click impatiently, trying to get Kicad to recognize the
> >> selection, the exception noted above is thrown.
> >>
> >> In parallel to all of this, I have noticed that with recent versions,
> >> pcbnew is slow to start up. In fact, a spinning beachball replaces the
> >> cursor for a little bit as it launches. And in some cases there is a
> >> slight delay between a mouse click and Kicad’s recognition of same. I
> >> wish I knew when this started. I first noticed it when using Adam’s
> >> nightlies, which I believe are configured to work on 10.7 and newer. I
> >> always build for whatever OS I’m actually running, so I do a build on
> >> my 10.10 laptop and my 10.9 iMac. My builds seem to run faster than
> >> Adam’s in this regard.
> >>
> >> Perhaps that slight startup delay is a red herring, I do not know.
> >>
> >> Anyways, what I think is happening is that before Kicad can display the
> >> correct context menu, it’s still processing mouse clicks and trying to
> >> put up another menu at the same time, and it gets all confused.
> >>
> >> ————————
> >>
> >> And dang-nabbit, right now I saw a new one. Again with the
> >> click-click-click-click on the edge cut line, finally the line
> >> properties dialog came up, and I went to change a coordinate, and bang
> >> — crash again. But this time it’s a new exception:
> >>
> >> NSInvalidArgumentException,
> >> reason: ‘Unlocking Focus on wrong view (<wxNSView:0x60800366fc0>),
> >> expected <wxNSButton: 0x608000563180>’
> >> abort() called
> >> terminating with uncaught exception of type NSException
> >>
> >> So I think maybe I have a poison build of wxWidgets, but it was also
> >> happening with Adam’s nightlies.
> >>
> >> -a
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> >> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> >> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> >
> >
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp