Jan Wielemaker

Rather odd. Thread 2 is the global object (atom,clause) garbage collector thread. This looks like the startup of this thread, trying to find the predicate to call. The module table...

Thanks for all the work. Concurrent dependency issues are not that likely to cause this. It doesn't match the crashes and concurrent builds are used on almost all platforms these...

As is, I think we should step back. I think there are two questions to answer first. 1) Does the ports(true) option lead to prohibitive expansion of the call tree...

> Don't intend to be argumentative, but this seems pretty theoretical to me. Sure it's possible to write such an example (construct and process million element lists?), but I have...

> I would hazard a guess that not very many Prolog users are dealing with hundreds of giga bytes of data. In my last academic job we had a machine...

Bottom line to me is whether you consider mutual recursive procedures on long lists to be something one finds in the wild. From the library, ord_union/3 is a perfect example....

> So I'm still unconvinced the classic mode is worth the added complexity, and building in more complexity doesn't really solve anything IMO. Only some of the port counts are...

This pull request has been mentioned on **SWI-Prolog**. There might be relevant details there: https://swi-prolog.discourse.group/t/using-format-2-with-attributed-variable-on-a-pengine/6996/18

This issue has been mentioned on **SWI-Prolog**. There might be relevant details there: https://swi-prolog.discourse.group/t/history-dependent-semi-lex-compare-3/6431/56

This issue has been mentioned on **SWI-Prolog**. There might be relevant details there: https://swi-prolog.discourse.group/t/fixing-the-compare-3-mirror-anomaly-in-swi-prolog/6438/4