Replies: 2 comments
-
|
I get the same error (and I did run "normalize platforms"). Did you find a solution? |
Beta Was this translation helpful? Give feedback.
0 replies
-
The above error is not related with RubyGems. Can you try it without jemalloc? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem as clearly as you can
Trying to run command 'bundle install' and output keeps asking me to open a ticket. Had me verify an issues did not already exist at :
https://github.com/search?q=repo%3Aruby%2Frubygems+%2Flib%2Fx86_64-linux-gnu%2Flibjemalloc.so.2++cannot+allocate+memory+in+static+TLS+block+-+%2Fvar%2Fwww%2Fmastodon%2Flive%2Fvendor%2Fbundle%2Fruby%2F3.4.0%2Fgems%2Fdate-3.4.1%2Flib%2Fdate_core.so&type=Issues
Did you try upgrading rubygems & bundler?
bundlerandrubygems.I've made sure everything is up to date
Running
gem update --systemshould get both installed on your system, and thenbundle update --bundlershould change your lockfile to use the new version ofbundler that was just installed.
It's likely that your issue has been fixed in recent versions, so just upgrading
might do the trick, and will also save us some time :)
Ruby version is 3.4.7 yet bundler keeps reporting ruby 3.4.1p0 ?
-->
Post steps to reproduce the problem
[In mastodon/live directory]
git fetch && git checkout 4.5.0-beta.2
bundle install
Which command did you run?
bundle install
What were you expecting to happen?
Having upgraded mastodon before, I've upgraded ruby before to match the mastodon releases, this is the first time this issue has occurred. Normally it just installs everything required so I can run
yarn install --immutablethen all I have to do is restart all the mastodon servicesWhat happened instead?
Beta Was this translation helpful? Give feedback.
All reactions