Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tizonia fails with MALLOC_PERTURB_ set #563

crobinso opened this issue Feb 16, 2019 · 2 comments


None yet
3 participants
Copy link

commented Feb 16, 2019

I'm running tizonia 0.17.0 via snap on Fedora 29.

tizonia was working for me with 'sudo snap run tizonia...', but not plain 'snap run...' either as regular user, or root via su -. After some trial and error it turns out the failure is due to the MALLOC_PERTURB_ environment variable which I set during login sessions but which isn't passed to sudo sessions. Explanation from my bash_profile:

# Tells glibc to clear memory requested via malloc, and after free. Helps
# catch crashes when developing. Remember you may hit crashes that others
# aren't hitting
MALLOC_PERTURB_=$(($RANDOM % 255 + 1))

I can work around it easy enough, but perhaps devs could try running with this option to see if they get similar failures. Possibly some use-after-free lingering.

The exact command and failure I'm seeing:

$ snap run tizonia --youtube-audio-stream
tizonia 0.17.0. Copyright (C) 2019 Juan A. Rubio
This software is part of the Tizonia project 

[YouTube] [Stream] 'Parasite Eve 1 Full OST [HQ Complete Original Soundtrack]' [webm].
[YouTube] [Stream] 'Parasite Eve 1 Full OST [HQ Complete Original Soundtrack]'.
[YouTube] [Streams in queue] '1'.

tizonia exiting (OMX_ErrorContentURIError).

 [Playlist not found]

This comment has been minimized.

Copy link

commented Feb 24, 2019

Hi!, thanks for reporting this issue.

Yes, I've been able to reproduce it. It looks like you need to export for CHECK_ and PERTURB_. Very interesting, I did not know about PERTURB_.

$ export MALLOC_CHECK_=3
$ export MALLOC_PERTURB_=$(($RANDOM % 255 + 1))

I'm marking this as a bug, to be fixed sometime soon.


This comment has been minimized.

Copy link

commented Feb 26, 2019

Fixes are now in the develop branch. To be released soon.

Closing this issue now. Thanks for reporting!

@tizonia tizonia closed this Feb 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.