Created attachment 1361731 [details]
File: backtrace

Created attachment 1361732 [details]
File: cgroup

Created attachment 1361733 [details]
File: core_backtrace

Created attachment 1361734 [details]
File: cpuinfo

Created attachment 1361735 [details]
File: dso_list

Created attachment 1361736 [details]
File: environ

Created attachment 1361737 [details]
File: limits

Created attachment 1361738 [details]
File: maps

Created attachment 1361739 [details]
File: open_fds

Created attachment 1361740 [details]
File: proc_pid_status

Created attachment 1361741 [details]
File: var_log_messages

Does this need specific steps to trigger or does pragha crash upon launching?

Never crashed upon launching.  All crashes have occurred some time after launch, while playing.

First symptom announcing something is going wrong: scrobbler plugin fails to upload the current song data to last.fm.  

Pragha keeps playing after showing the plugin failure message, but crashes after a while (not necessarily on that very same song where scrobbling started failing).  Every song played after the first scrobbling failure also fails to be scrobbled, until pragha crashes.

Music file type/data/tags do not seem to be the culprit, since the same files can be played and scrobbled OK most times; and i haven't managed to make it crash two times playing the exact same files.

Similar problem has been detected:

Played and scrobbled OK some 30 music files.  Left it idle for about 20 hours.
Started playing some more files (about 3 or 4 more), and they weren't scrobbled.  
Pragha finished playing them all and went idle again, then crashed several minutes after.

Found this in ~/.xsession-errors:
pragha: malloc.c:2845: mremap_chunk: Assertion `((size + offset) & (GLRO (dl_pagesize) - 1)) == 0' failed.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        pragha
crash_function: myrealloc
executable:     /usr/bin/pragha
journald_cursor: s=9922d4ec231847fc80a0b5cfc5e6bbaa;i=17b082;b=7d96db308b194f75aecf48c7c402208a;m=4098a7a881;t=55f9ccd77ffcf;x=465498c7d9143c38
kernel:         4.13.16-200.fc26.x86_64
package:        pragha-1.3.3-6.fc26
reason:         pragha killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.