-
Notifications
You must be signed in to change notification settings - Fork 411
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
Memory allocation of x bytes failed error🐛 #1018
Comments
Also seeing this on macOS Monterey (12.3) |
Also seeing this on Pop OS 22.10. |
Hi all, is it this that you're hitting? #878 (comment) If it's different from #878, can you provide
|
@saumyajyoti do you see the same problem with previous delta versions? Can you try
I do think that this sounds similar to #878 so please take a look at discussion in that issue and the linked syntect issue. FWIW I've tested installing 0.12.1 on MacOS Intel 11.6.4 (BigSur) via Homebrew and that did not have this problem. |
Thanks. This step resolved the issue. :) |
@dandavison, for me it doesn't resolve the issue.
I have tried |
Hi @lalitmee. OK, if you have time to investigate this further, perhaps you could try uninstalling the version you installed and installing a previous delta version and determining which versions it is reproducible on? |
@dandavison, for me |
This worked 🚀
This is the step that causes delta to fail 💥
@dandavison can this issue be re-opened until a proper fix is available? Probably not sharing bat's cache. |
Downloaded bat v0.20.0 from GH, rebuilding cache with this version doesn't cause issues to delta. System's bat does complain about the cache:
|
Thanks very much @awerlang -- I think with what you've said we have an understanding of this problem: I believe that delta docs need to say something like: If you are using bat, then you need to ensure that bat and delta are both on compatible versions. Currently, this means either
For Delta users, after changing bat & delta version, please run
I believe those bat versions are correct but not 100% sure. @lalitmee would you be able to move your system into a state that conforms with the above?
I'm hoping not to have to do that right now. With bat v0.20.0 delta is now using bat as a library so should always be able to keep up with any backward-incompatible changes that bat makes simply by incrementing the bat library version. Users of delta and bat would have to upgrade both together, but I believe that such backward-incompatible changes are rare (the recent one was the first one we've seen in the 2 years or so that delta's been alive; I believe it's due to the lazy theme loading introduced in https://github.com/sharkdp/bat/releases/tag/v0.19.0)
Just to make it clear for anyone else reading this -- our advice would be not to run two bat versions on your system for this reason. |
Packagers will need to be aware of this relationship. Vendoring makes this a bit harder to manage though.
Somewhat related I proposed this on bat's side sharkdp/bat#2085 (comment) |
I just wanted to give a heads-up that an upcoming release of bat will begin to also lazy-load syntaxes, which will constitute another breaking change in the same way that lazy-loading of themes did. Essentially, bat makes no guarantees about backwards compatibility between 0.x.0 releases. But in practice we try to be somewhat nice about backwards compatibility even between 0.x.0 releases. |
This is still an issue with current versions:
This is on Arch with the repo versions. |
Hi @aperum, can you try upgrading to the latest bat (v0.21.0) and rebuilding your cache? |
With 0.21.0 it works. Should have checked for a newer version upstream, sorry for the noise. |
(You can use
git --no-pager
to produce the raw text output.)Thanks for filing a Delta bug report!
Any DELTA command fails with above error on Windows 11 latest insider build.
The text was updated successfully, but these errors were encountered: