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

Double free error while updating #193

Open
bma-vandijk opened this issue Jan 8, 2021 · 2 comments
Open

Double free error while updating #193

bma-vandijk opened this issue Jan 8, 2021 · 2 comments
Assignees
Labels

Comments

@bma-vandijk
Copy link

Hi,

I stumbled upon some other thing while running a LaMachine update which I think I'm not really equipped to handle.

fatal: [LAPTOP-5N7G0RHD.localdomain]: FAILED! => {
"changed": false,
"cmd": "#!/bin/bash\nexport LM_QUIET=1\nif [ -e /home/bmavd/bin/lamachine-lama-activate ]; then\n source /home/bmavd/bin/lamachine-lama-activate\nelse\n echo "Activation script /home/bmavd/bin/lamachine-lama-activate not found! ">&2\n exit 2\nfi\nhash -r #clear cache\necho "Run environment:">&2\necho " LM_NAME=$LM_NAME">&2\necho " PATH=$PATH">&2\necho " LD_LIBRARY_PATH=$LD_LIBRARY_PATH">&2\necho " VIRTUAL_ENV=$VIRTUAL_ENV">&2\necho " PYTHONPATH=$PYTHONPATH">&2\necho " PYTHON=$(which python3)">&2\necho " PIP=$(which pip3)">&2\necho " LANG=$LANG">&2\necho " LC_ALL=$LC_ALL">&2\necho "Running: python3 -c 'import frog'">&2\npython3 -c 'import frog'\n",
"delta": "0:00:00.379054",
"end": "2021-01-08 09:39:13.476208",
"rc": -6,
"start": "2021-01-08 09:39:13.097154"
}

STDERR:

Run environment:
LM_NAME=lama
PATH=/home/bmavd/lama/bin:/home/bmavd/bin:/home/bmavd/lama/bin:/home/bmavd/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files/WindowsApps/CanonicalGroupLimited.UbuntuonWindows_2004.2020.812.0_x64__79rhkp1fndgsc:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath:/mnt/c/Python38/Scripts/:/mnt/c/Python38/:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Program Files/NVIDIA Corporation/NVIDIA NvDLISR:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/dotnet/:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Users/bma-v/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/bma-v/AppData/Roaming/Python/Python38/Scripts:/mnt/c/Users/bma-v/AppData/Local/GitHubDesktop/bin:/mnt/c/Users/bma-v/.dotnet/tools:/snap/bin
LD_LIBRARY_PATH=/home/bmavd/lama/lib/:/home/bmavd/lama/opt/Alpino/create_bin/extralibs/boost:/home/bmavd/lama/opt/Alpino/create_bin/extralibs
VIRTUAL_ENV=/home/bmavd/lama
PYTHONPATH=
PYTHON=/home/bmavd/lama/bin/python3
PIP=/home/bmavd/lama/bin/pip3
LANG=C.UTF-8
LC_ALL=en_US.UTF_8
Running: python3 -c 'import frog'
free(): double free detected in tcache 2

MSG:

non-zero return code

In Python I can still use the python-frog binding and properly parse text, but when I try to exit Python I get the following output:

double free or corruption (fasttop)
lAborted

Thanks in advance for your help.

log:
lamachine-lama-20210108_092746.log

@proycon
Copy link
Owner

proycon commented Jan 8, 2021

That is a indeed a nasty issue we have seen before in rare circumstances, see proycon/python-frog#17 .

It's a bit of a mystery still what causes it, usually it doesn't occur. Can you try the suggested solution there by explicitly removing the installed python-frog prior to running lamachine-update?

@proycon proycon self-assigned this Jan 8, 2021
@bma-vandijk
Copy link
Author

Hello,

Not sure whether I understood your tips correctly but this is what I did:

I tried updating (both normal and with force=1) after
-deleting the frog.cpython-38-x86_64-linux-gnu.so file from the site-packages dir
-deleting the python-frog folder in the lama/src folder

in both cases the folders/files were replaced after updating but the updating is still aborted with the same error. It seems I can still use Frog. Yet, while working in JupyterLab I have the feeling that Frog freezes the kernel sometimes (after reboot it usually works again) and that it may have to do something with this error.

Thanks in advance

lamachine-lama-20210110_113317.log

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

No branches or pull requests

2 participants