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

[Ubuntu] Issue with libstdc++ cannot allocate memory in static TLS block #4799

Closed
2 of 7 tasks
miketimofeev opened this issue Dec 23, 2021 · 4 comments
Closed
2 of 7 tasks

Comments

@miketimofeev
Copy link
Contributor

miketimofeev commented Dec 23, 2021

Breaking changes

Due to a bug in MySql 8.0.27 (https://bugs.mysql.com/bug.php?id=105288) we had to revert the version to 8.0.26 yet it's not possible to use ubuntu upstream repo as it doesn't contain older versions. In this PR we switched the installation to install all the dependencies step by step utilizing the dpkg -i command #4674

This leads to unpredictable behavior in libstdc++ usage when calling from Python (there could be other cases we are not aware of) — #4733, #4790
Please use the provided workaround until we either got 8.0.26 in the upstream repo or the new version 8.0.28 is released.

Possible impact

If your Python code uses some C++ libraries it can be broken.

Virtual environments affected

  • Ubuntu 18.04
  • Ubuntu 20.04
  • macOS 10.15
  • macOS 11
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

Mitigation ways

Reinstall MySQL version 8.0.27 using upstream repo:

sudo apt-get update
sudo apt-get remove mysql* && sudo apt-get install -y mysql-server
@RW21
Copy link

RW21 commented Jan 24, 2022

To add to the mitigation method provided, if you are using Python's mysql-client, you will need to install libmysqlclient-dev, otherwise you will get OSError: mysql_config not found.
So:

    - name: GA fixes
      run: |
        sudo apt-get update
        sudo apt-get remove mysql* && sudo apt-get install -y mysql-server libmysqlclient-dev

@actions actions deleted a comment from Misshunter1 Jan 24, 2022
@actions actions deleted a comment Feb 14, 2022
techouse added a commit to techouse/mysql-to-sqlite3 that referenced this issue Feb 18, 2022
techouse added a commit to techouse/mysql-to-sqlite3 that referenced this issue Feb 18, 2022
techouse added a commit to techouse/mysql-to-sqlite3 that referenced this issue Feb 18, 2022
techouse added a commit to techouse/sqlite3-to-mysql that referenced this issue Feb 18, 2022
@actions actions deleted a comment from anthillofoppies44 Feb 24, 2022
@miketimofeev miketimofeev pinned this issue Feb 25, 2022
@marcelgerber
Copy link
Contributor

I think this issue can be fixed by now, right?
The underlying bug is fixed in 8.0.28, and 8.0.28 is available from apt in 20.04 LTS. So simply reverting #4674 should do the trick.

@miketimofeev
Copy link
Contributor Author

thanks @marcelgerber for the update!
We will test the behavior to make sure it's is really fixed and then rollback the workaround 🙂

@miketimofeev
Copy link
Contributor Author

@marcelgerber we have reverted mysql client installation to the upstream repo, this shouldn't be the issue anymore.

marcelgerber added a commit to owid/etl that referenced this issue Apr 12, 2022
@miketimofeev miketimofeev unpinned this issue Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants
@marcelgerber @RW21 @miketimofeev @mikhailkoliada @ddobranic and others