[Wireshark-bugs] [Bug 12470] Segfault when too many recent capture files registered

2019-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12470 --- Comment #4 from Jaap Keuter --- The latest build 2.6.7 with GTK+ 3.24.2 doesn't exhibit this issue anymore. So leaving this RESOLVED/FIXED sounds good to me. -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 12470] Segfault when too many recent capture files registered

2019-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12470 Christopher Maynard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12470] Segfault when too many recent capture files registered

2019-01-14 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12470 --- Comment #3 from Christopher Maynard --- (In reply to Jaap Keuter from comment #2) > Adding a 19th item to the recent.capture_file list in recent_common causes > Wireshark (GTK) to crash at startup, with attached backtrace. I could

[Wireshark-bugs] [Bug 12470] Segfault when too many recent capture files registered

2016-05-25 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12470 --- Comment #2 from Jaap Keuter --- Created attachment 14595 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14595=edit Backtrace after crash Adding a 19th item to the recent.capture_file list in

[Wireshark-bugs] [Bug 12470] Segfault when too many recent capture files registered

2016-05-25 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12470 --- Comment #1 from Michael Mann --- Could not duplicate on Windows (32-bit) although I did notice that at 18 capture files is when the startup screen starts to add a scrollbar for the recent list "window" (that