Can you see if this commit fixes it for you?

https://gitlab.com/wireshark/wireshark/-/commit/0146fe4eb622a6a54d6ccb0e69488b594ec1fe50

John Thacker

On Wed, Jul 10, 2024, 6:17 PM Ben Greear <gree...@candelatech.com> wrote:

> Hello,
>
> We saw a lockup on a system with lots of network interfaces.
> I haven't looked at the code, but it smells like a somewhat common pipe
> related lockup
> where the child process is trying to write, but parent is not reading
> because it is
> waiting for child to complete, so child cannot finish writing and exit,
> so...deadlock.
>
> Any ideas on this?  Our build is a bit old, so we'll pull latest and see if
> it is reproducible...
>
> [root@ct523c-2175 ~]# wireshark --version
> Wireshark 4.3.0 (Git commit 2ae6c42ce290).
>
> wireshark:
>
> (gdb) bt
> #0  0x00007f7ab3edccbf in wait4 () from /lib64/libc.so.6
> #1  0x00005636a4d31d66 in sync_pipe_wait_for_child.lto_priv ()
> #2  0x00005636a4d4ff06 in sync_interface_stats_open.constprop ()
> #3  0x00005636a4ab6334 in InterfaceFrame::scanLocalInterfaces(_GList*) ()
> #4  0x00007f7abd3b1385 in void doActivate<false>(QObject*, int, void**) ()
> from /lib64/libQt6Core.so.6
> #5  0x00005636a49caac6 in MainApplication::scanLocalInterfaces(_GList*) ()
> #6  0x00005636a4994c0a in main ()
> (gdb)
>
> dumpcap (what is being waited upon):
>
> (gdb) bt
> #0  0x00007f7182301c37 in write () from /lib64/libc.so.6
> #1  0x00007f718228496d in _IO_file_write@@GLIBC_2.2.5 () from
> /lib64/libc.so.6
> #2  0x00007f7182283d10 in new_do_write () from /lib64/libc.so.6
> #3  0x00007f71822859d9 in __GI__IO_do_write () from /lib64/libc.so.6
> #4  0x00007f7182283b48 in __GI__IO_file_sync () from /lib64/libc.so.6
> #5  0x00007f718227944c in fflush () from /lib64/libc.so.6
> #6  0x0000563c67f170a9 in print_statistics_loop ()
> #7  0x0000563c67f118e9 in main ()
> (gdb)
>
> Thanks,
> Ben
>
> --
> Ben Greear <gree...@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to