/usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6214176f5dcd8b5e97adde63323ccb09827d853c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

[Max Wittal (madmax43v3r)]

This bug is triggered when many new files are added to the folder in which an image is opened.

(eog:6555): GLib-WARNING **: 23:38:42.199: Accessing a sequence while it is being sorted or searched is not allowed

(eog:6555): GLib-WARNING **: 23:38:42.200: Accessing a sequence while it is being sorted or searched is not allowed
corrupted size vs. prev_size
Aborted (core dumped)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

Thanks for the comment, could you give details on the number/type of files and how they get copied? Can you trigger it easily or was it a one time thing?

[Sebastien Bacher (seb128)]

What version of Ubuntu do you use? The errors page shows no report since 17.10

[Max Wittal (madmax43v3r)]

I'm running Ubuntu 19.04, and I did send the bug report.

It is 100% reproducible, I have a folder which an application is writing about ~100 new PNG images per second into (ie. new image files added to the folder), up to about 100,000 images. If I try to open one of those images _during_ this process the bug is triggered 100%. If I open an image after the process is finished it works just fine.

[Sebastien Bacher (seb128)]

Could you look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

[Max Wittal (madmax43v3r)]

https://errors.ubuntu.com/oops/b9742d32-072f-11ea-aff5-fa163e983629
https://errors.ubuntu.com/oops/4c711916-072a-11ea-b6b3-fa163e102db1

[Sebastien Bacher (seb128)]

Thanks, trying to reproduce with a cp loop it does seem to create issues but not that segfault. Do you have plugins installed/enabled? What UI elements are displayed? (gallery, sidebar, ...)?

[Sebastien Bacher (seb128)]

Got it once with the cp loop and starting eog on one file while it was copying

[Max Wittal (madmax43v3r)]

No plugins as far as I know. Also no UI elements.

It doesn't look like a segfault, but rather a failed assert() in glibc.

[Max Wittal (madmax43v3r)]

I think the more files you already have in the folder the higher the chance that another new file will trigger the bug. The more time it needs to sort the list the more time for the race condition to occur, and each new file is another shot.

[Sebastien Bacher (seb128)]

bug #1840508 looks like the same report. Let's close this one since the error tracker reference has no report since 17.10 which suggests that even if the error is similar that was probably a different problem