| ID: | 4478 |
| From: | ge...@igor2.repo.hu |
| Date: | Tue, 27 Oct 2020 12:21:40 +0100 (CET) |
| Subject: | Re: [pcb-rnd] Strange lockups |
| in-reply-to: | 4475 from Majenko Technologies <ma...@majenko.co.uk> |
| replies: | 4479 from Majenko Technologies <ma...@majenko.co.uk> |
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --722076672-803909708-1603797700=:3584 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Tue, 27 Oct 2020, Majenko Technologies wrote: >I have recently been experiencing a couple of random lockups with PCB-RND. I >haven't yet got to the bottom of it, and it's proving hard to replicate. >It always happens when navigating a menu though, and it freezes the whole >window manager with the menu half displayed (the *whole* window manager - >can't select any other windows, or anything). To do anything I have to kick >out to a console and kill pcb-rnd at which point my X session becomes >responsive again. > >I don't know yet whether this is just a quirk with my system or something in >PCB-RND. I'll keep digging and give more detail as I find it, but this is >really just a heads up that there might be something up with menus. Once I >can replicate it more reliably I can try various options like different HIDs >to see if that makes a difference. If the whole WM freezes, you most likely have something real bad outside of pcb-rnd: in a UNIX system we expect a process can crash, go in infinite loop, do rnadom stupid things, but that shouldn't affect global resources and other processes. Of course that doesn't mean we don't have a bug on our side that triggers it, but I can't imagine a situation where it's legitimate that a pcb-rnd bug hangs your whole WM. If you did not click on any menu item that'd execute an action, only opened menus and moved around, you did not tear off any menu to cause it, then it's even further away from pcb-rnd: both in gtk and in lesstif we replicate the internal menu structure into the toolkit's menu system and from then on we leave the toolkit to handle the menu system. We only touch the toolkit's menu system again when you change some config setting that has a checkbox in a menu or if we need to insert/remove menu items. But if you are not doing anything that changes states, it's all gtk and the WM in your case. Please try these, when you have the lockup and switched to the console: - look at CPU consumption of pcb-rnd itself - if CPU is spinning on 100% on your pcb-rnd process, also look at the memory footprint; the important aspect is not the current absolute memory usage, but whether it's constantly growing or not - configure with --debug and attach a gdb to the running process when you already have the lockup and capture a backtrace; if you can produce this multiple times, please always save a backtrace, so we see if it's always the same TIA, Igor2 --722076672-803909708-1603797700=:3584--
Reply subtree:
4478 Re: [pcb-rnd] Strange lockups from ge...@igor2.repo.hu
4479 Re: [pcb-rnd] Strange lockups from Majenko Technologies <ma...@majenko.co.uk>