bad_alloc in vamp_plugins

[mixxxbot]

Reported by: mk42
Date: 2016-01-06T11:35:43Z
Status: Expired
Importance: Medium
Launchpad Issue: lp1531467
Tags: vamp
Attachments: [Backtrace of all threads when crashing/starting mixxx](https://bugs.launchpad.net/bugs/1531467/+attachment/4544898/+files/Backtrace of all threads when crashing/starting mixxx)

---

the current master (2.1) and also 2.0 (1.12) isn't starting for me anymore. Ive just recompiled it because my installed versions complains about some undefined symbols related to google (i think due to a system update).

The freshly built git head b772599 is terminating during startup with

Debug [Main]: Loading resources from  "./res/" 
Debug [Main]: Setting VAMP_PATH to:  "/home/mk/git/mixxx/lin64_build/vamp-plugins:/usr/local/lib/mixxx/plugins/vamp:/home/mk/git/mixxx/lin64_build/vamp-plugins:/usr/local/lib/mixxx/plugins/vamp:/home/mk/git/mixxx/lin64_build/vamp-plugins" 
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Abgebrochen (Speicherabzug geschrieben)

gdb gives the attached backtrace. I think its thread 1 that causes the problem.

Is is because of systemwide installed libraries? I can't figure out why this happens.
I'm on arch with vamp-plugin-sdk 2.5-3 installed.

1.12 (3dae24c) is facing the same error and backtrace

Any thoughts?

[mixxxbot]

Commented by: mk42
Date: 2016-01-06T11:35:43Z
Attachments: [Backtrace of all threads when crashing/starting mixxx](https://bugs.launchpad.net/mixxx/+bug/1531467/+attachment/4544898/+files/Backtrace of all threads when crashing/starting mixxx)

[mixxxbot]

Commented by: mk42
Date: 2016-01-06T12:32:30Z

---

I've done scons install and now it runs again. Isn't mixxx using the vamp-plugins directory over the system wide installed plugins?

[mixxxbot]

Commented by: Be-ing
Date: 2018-12-30T19:08:14Z

---

Probably fixed now that VAMP plugins have been removed:
#926

[mixxxbot]

Commented by: rryan
Date: 2018-12-30T19:26:31Z

---

It still affects 2.1.x and potentially 2.2.x, so I don't think we can call it fixed. We haven't had anyone report this in 2 years, so maybe let's leave it as incomplete, then if someone else confirms it we can see if it's worth attempting to fix in 2.2.x.

[mixxxbot]

Commented by: janitor
Date: 2019-03-01T04:17:21Z

---

[Expired for Mixxx because there has been no activity for 60 days.]

[mixxxbot]

Issue closed with status Expired.