Control: tag -1 + moreinfo

Hi Samuel !

On Thu, Aug 30, 2018 at 03:30:14PM +0200, Samuel Hym wrote:
> Dear Maintainer,
> I ran "opam init" on my little machine that has only 2GB of RAM and
> had to kill it after gringo had gobbled all the available memory.
> I just tried on a bigger computer to see that it peaks at 3 or 4GB,
> making it unusable on small machines.
> I wondered why, and how to mitigate this: maybe gringo is not the best
> default choice for the chain of dependencies (opam -> aspcud ->
> gringo) in opam's case? Is it a bug in opam 2 (I had not noticed a
> problem with the previous version), giving a terrible problem to solve

Can you try giving the flag --use-internal-solver to opam ?

This is a bit surprising, as (according to Ralf) opam now defaults to its
internal solver, see bug #908203.



Attachment: signature.asc
Description: PGP signature

Reply via email to