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

Segmentation Fault / malloc errors #146

Open
ttaong opened this issue Jan 31, 2020 · 1 comment
Open

Segmentation Fault / malloc errors #146

ttaong opened this issue Jan 31, 2020 · 1 comment

Comments

@ttaong
Copy link

ttaong commented Jan 31, 2020

Hi @k2kobayashi,

Thanks for the wonderful library you've built. I'm trying to use it to synthesise some voices for a video game.

While running:
python3 example/initialize.py -3 DEMON FAIRY 16000

I'm running into two errors - one about malloc and another about segmentation fault

=== MALLOC ERROR===
python3(25887,0x108c7c5c0) malloc: Incorrect checksum for freed object 0x7fb534175e00: probably modified after being freed.
Corrupt value: 0x401f13f9ffb0cfed
python3(25887,0x108c7c5c0) malloc: *** set a breakpoint in malloc_error_break to debug

=== SEG FAULT ERROR===
1] 26095 segmentation fault python3 example/initialize.py -3 DEMON FAIRY 16000

I have tried to debug and it is going into pyworld library.
When the code in https://github.com/k2kobayashi/sprocket/blob/master/sprocket/speech/analyzer.py
is being executed, the lines 57 and 59 cause these problems. Usually segmentation fault occurs while computing 'spc' using pyworld.cheaptrick and malloc error occurs while computing 'ap' using pyworld.d4c methods.

Also note that this does not happen always. Sometimes it analyses the first few audio files and then crashes with one of the two errors. Every run, a different number of audio files are analysed before crashing.

Not sure is this issue - #17 is related to this one.
Any idea how I can overcome this? Any help is appreciated. Thanks!

@egaznep
Copy link

egaznep commented Jan 25, 2021

I experienced this too. I feel that different parameter configurations cause this problem (e.g. setting a FFT length which is not a power of 2). I'll invest few hours to find the problem and if I solve I'll let you know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants