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

[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 changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

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

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12470

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

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

[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 not reproduce this problem with Wireshark 2.6.6 on Windows 64-bit
running either the GTK+ or Qt UI's.  It would appear this bug has been fixed?

If you can reproduce the crash with the latest stable version of Wireshark and
Qt UI, then we can change the component to Qt UI, but if you can only reproduce
it with the GTK+ UI, then we should close it as "WONTFIX" since that UI is no
longer supported.  Of course if you can't reproduce it at all, then I guess we
can just close it as "FIXED".

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

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

[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 recent_common causes
Wireshark (GTK) to crash at startup, with attached backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

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

[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 doesn't look like a window until the scroll bar is
added).  I was hoping to find something like a MAX_RECENT_ITEMS #define, but it
all looks pretty dynamic to me.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe