Created attachment 1389700 [details]
File: backtrace

Created attachment 1389701 [details]
File: cgroup

Created attachment 1389702 [details]
File: core_backtrace

Created attachment 1389703 [details]
File: cpuinfo

Created attachment 1389704 [details]
File: dso_list

Created attachment 1389705 [details]
File: environ

Created attachment 1389706 [details]
File: limits

Created attachment 1389707 [details]
File: maps

Created attachment 1389708 [details]
File: mountinfo

Created attachment 1389709 [details]
File: open_fds

Created attachment 1389710 [details]
File: proc_pid_status

Reproducible?

Forwarded upstream to inform them:
https://redmine.audacious-media-player.org/issues/775

You've managed to crash libstdc++ internally due to bad memory allocation size.

#6  0x00007fac4faf542c in operator new(unsigned long) (sz=94132798226440) at ../../../../libstdc++-v3/libsupc++/new_op.cc:54
        handler = <optimized out>
        p = <optimized out>

I was not able to figure out the problem from the backtrace.  Could you reproduce it with AMPACHE_BROWSER_PLUGIN_VERBOSITY environment variable set to '4', like this:

$ AMPACHE_BROWSER_PLUGIN_VERBOSITY=4 audacious -VVQ > audacious.log 2>&1

and provide the resulting 'audacious.log' file, please?

The xml file that Nextcloud server sends to the plugin would also be helpful.  You can get it by following steps:

Store current time:

$ tm=`date +%s`

Get passphrase (replace <password>):

$ echo -n $tm$(echo -n <password> | sha256sum | cut -d " " -f 1) | sha256sum
5854ad1eabbaaaa1ed3e48a143d3d3d4e26c63d5950a359bfde5c133dcadf4c5  -

Authenticate to the server (replace the passphrase and <user_name>).  Server will return authentication token:

$ curl "https://cemit.mysel:40015/ampache/server/xml.server.php?action=handshake
&auth=5854ad1eabbaaaa1ed3e48a143d3d3d4e26c63d5950a359bfde5c133dcadf4c5&timestamp
=${tm}&version=350001&user=<user_name>"
<?xml version="1.0" encoding="UTF-8" ?>
<root>
        <auth><![CDATA[af806767fcad09b573a3aa6085564d3c]]></auth>
        <api><![CDATA[380001]]></api>
...

Get artists xml using the token (here limited to 1000 entries) (replace auth token):

$ curl "https://cemit.mysel:40015/ampache/server/xml.server.php?action=artists&a
uth=af806767fcad09b573a3aa6085564d3c&offset=0&limit=1000" > artists.xml

Proper upstream tracking address is: https://github.com/ampache-browser/ampache_browser/issues/6.

Created attachment 1407930 [details]
Detailed log file

Sorry about the delay.

Created attachment 1407931 [details]
Artists response xml

The bug is fixed in the source repository, branch v1.0 [1].  Changeset 3f1b36674032b6c93dcda779132918fb3aff0587 can be used for testing.

Please be aware that Nextcloud's Music app ignores 'limit' parameter when talking to the client which may cause performance degradation of Ampache Browser during loading.  Also it sends wrong timestamp of last modification of the media collection so caching in Ampache Browser will not work.

Thanks for the report and all the additional debug info.

1. https://github.com/ampache-browser/ampache_browser/tree/v1.0

ampache_browser-1.0.0-3.20180408.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b60fb0f2bb

ampache_browser-1.0.0-3.20180408.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b60fb0f2bb

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.