Bug 1426166

Created attachment 1272256 [details]
reproducer.tar.gz

Still a problem with version 0.6.12-1. Here is output of coredumpctl when a segmentation fault happened when run on the data in reproducer.tar.gz. coredump is attached.

clime@coprbox ~/appstream-builder-testing $ coredumpctl dump > dump
           PID: 15060 (appstream-build)
           UID: 1000 (clime)
           GID: 1000 (clime)
        Signal: 11 (SEGV)
     Timestamp: Tue 2017-04-18 11:12:07 CEST (2min 26s ago)
  Command Line: /usr/bin/appstream-builder --add-cache-id --max-threads=4 --temp-dir=reproducer-data/tmp --cache-dir=reproducer-data/cache --packages-dir=reproducer --output-dir=reproducer-data/appdata --basename=appstream --include-failed --min-icon-size=48 --enable-hidpi --origin=orpiske/orp-tools-testing
    Executable: /usr/bin/appstream-builder
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (clime)
       Boot ID: 23abaab67d7a48cba55ed126044dac52
    Machine ID: 9679efdf5f3640a5a8ce07269a65fc4f
      Hostname: coprbox.den
      Coredump: /var/lib/systemd/coredump/core.appstream-build.1000.23abaab67d7a48cba55ed126044dac52.15060.1492506727000000000000.lz4
       Message: Process 15060 (appstream-build) of user 1000 dumped core.
                
                Stack trace of thread 15060:
                #0  0x00007f604ed451f7 as_format_get_kind (libappstream-glib.so.8)
                #1  0x00007f604ed55185 as_store_add_app (libappstream-glib.so.8)
                #2  0x00007f604eb1337c asb_context_add_app_ignore (libappstream-builder.so.8)
                #3  0x00007f604eb1374c asb_context_process (libappstream-builder.so.8)
                #4  0x000055e37ce1537d main (appstream-builder)
                #5  0x00007f604abac401 __libc_start_main (libc.so.6)
                #6  0x000055e37ce158ca _start (appstream-builder)
                
                Stack trace of thread 15062:
                #0  0x00007f604ac8dbf9 syscall (libc.so.6)
                #1  0x00007f604b6c89df g_cond_wait (libglib-2.0.so.0)
                #2  0x00007f604b65790b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
                #3  0x00007f604b6ab6dd g_thread_pool_thread_proxy (libglib-2.0.so.0)
                #4  0x00007f604b6aab93 g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f604af596ca start_thread (libpthread.so.0)
                #6  0x00007f604ac93f7f __clone (libc.so.6)
                
                Stack trace of thread 15063:
                #0  0x00007f604ac8dbf9 syscall (libc.so.6)
                #1  0x00007f604b6c89df g_cond_wait (libglib-2.0.so.0)
                #2  0x00007f604b65790b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
                #3  0x00007f604b6ab6dd g_thread_pool_thread_proxy (libglib-2.0.so.0)
                #4  0x00007f604b6aab93 g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f604af596ca start_thread (libpthread.so.0)
                #6  0x00007f604ac93f7f __clone (libc.so.6)
                
                Stack trace of thread 15064:
                #0  0x00007f604ac8dbf9 syscall (libc.so.6)
                #1  0x00007f604b6c89df g_cond_wait (libglib-2.0.so.0)
                #2  0x00007f604b65790b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
                #3  0x00007f604b6ab6dd g_thread_pool_thread_proxy (libglib-2.0.so.0)
                #4  0x00007f604b6aab93 g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f604af596ca start_thread (libpthread.so.0)
                #6  0x00007f604ac93f7f __clone (libc.so.6)
                
                Stack trace of thread 15061:
                #0  0x00007f604ac8dbf9 syscall (libc.so.6)
                #1  0x00007f604b6c89df g_cond_wait (libglib-2.0.so.0)
                #2  0x00007f604b65790b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
                #3  0x00007f604b6ab6dd g_thread_pool_thread_proxy (libglib-2.0.so.0)
                #4  0x00007f604b6aab93 g_thread_proxy (libglib-2.0.so.0)
                #5  0x00007f604af596ca start_thread (libpthread.so.0)
                #6  0x00007f604ac93f7f __clone (libc.so.6)
More than one entry matches, ignoring rest.

Actually, I cannot attach the core dump file because it's very large. It's now to be downloaded here http://clime.cz/coredump-appstream-build

Also, I am sorry for not very nice bug reports here. I probably should have packed the coredumpctl output to a file.

I get occassional crashes even with this simple command: 

$ while true; do /usr/bin/appstream-builder --add-cache-id --temp-dir=reproducer-data/tmp --cache-dir=reproducer-data/cache --packages-dir=reproducer --output-dir=reproducer-data/appdata --basename=appstream; done

Output is:

(appstream-builder:25826): As-WARNING **: no format specified in */package/*/*/litestomp.i686/*

(appstream-builder:25826): As-WARNING **: no format specified in */package/*/*/litestomp.i686/*
Segmentation fault (core dumped)

but when I remove --add-cache-id option, the problem seems to dissappear.

So the issue is probably related to `--add-cache-id`.

I'll do some more debugging on this today, but I don't think you want to be using --add-cache-id on COPR anyway IMHO.

Please, can you briefly explain what `--add-cache-id` does or where I can find more info about it? More specifically, what is component 'cache ID' good for in the appstream data?

Thank you!

(In reply to clime from comment #6)
> Please, can you briefly explain what `--add-cache-id` does

Sure! The CacheID was used to recover partial result using previous AppStream files, the idea being that you could run appstream-builder on a folder of rpms and it would only extract and build the ones changed compared to yesterday, and then merge it back into the AppStream file. This was designed so it could be possible to run the job on koji after every build, rather than doing it on a different server once per day. Mapping the component ID to the filename then became required, hence adding the cache-id (the rpm filename) to the metadata. Unfortunately, the results when using the partial update were not always the same as doing a fresh run (some components depend on other components) and it was decided that actually it wasn't so important to get the process running on koji, so even I'm not using cache-id anymore when running appstream-builder on the whole of Fedora, on all branches. The other reason for it not running on fedora infra is that we mirror the screenshots (for privacy) which would require koji to download random PNGs from the internet, which was a no-go.

I'm probably going to remove the --cache-id mode from git soon, as it's confusing people and introducing subtle bugs.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.