Hi! Sorry I forgot to mention that, but: I'm still not sure how to reliably reproduce; but I'll try your approach as soon as I can.
Best regards, Marcus On Tue, 2018-01-23 at 05:50 -0500, Jeff Long wrote: > You could try removing the bus_structure_source from the GRC file to see if > it's somewhere in that logic. > > On Tue, Jan 23, 2018 at 5:37 AM, Müller, Marcus (CEL) <[email protected]> wrote: > > Hello everyone, > > > > I'm currently debugging a strange spinlooping issue in GRC, which > > happened just while I was entering the number of output streams in a > > PFB channelizer's property dialog; I've not pressed enter or closed the > > dialog. > > > > However, as far as my htop and gdb debugging goes, the code path taken > > by python now loops. A significant amount of times it seems to cross > > through grc/giui/Port.py:68, create_shapes() and the calling > > Element.py, as ultimatively called by grc/gui/FlowGraph.py:477 update() > > (typical backtrace att.). > > > > Any pointers on how to further debug this? I feel like update() is > > triggered by some change in the output connectors of the block, but the > > update() itself causes the output connectors to force an update. > > > > Best regards, > > Marcus > > _______________________________________________ > > Discuss-gnuradio mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
