Computer shuts down and restarts on cmake install

[onecable5781]

Hello,

I have a Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz with 8 GB RAM running Ubuntu 24.04.1 LTS.

I have tried this multiple times but each time the computer shuts down and restarts at this exact step:

(1) Extract zip file to folder. cd into that folder
(2) cmake -S . -B build -DBUILD_DEPS=ON
(3) cmake --build build --config Release --target all -j -v

Here, it stops with high cpu utilization after the following:

...
[8%] linking cxx static library ../lib/libabs1_spinlock_wait.a
...
[8%] building cxx object _deps/highs-build/src/CMakeFiles/highs.dir/mip/HighsNodeQueue.cpp.o
...
[8%] built target utf8_range
gmake[2]: leaving directory .../build

Is there something highly computing intensive which goes on after this step which could be causing this? Is there a way I can provide more information to the developers to see what is going on? Or is it that my infrastructure is too weak to support or tools.

Thanks.

[sschnug]

Sadly this is not really an issue to be targeted by the developers: this is just a basic build-toolchain which should not be able to crash a system (at most: memory-trashing).

If your machine crashes, it's probably broken:

• thermal-management / overheating (compilation is cpu-heavy)
• damaged system-memory (compilation is RAM-heavy)
• damaged HDD (compilation is IO-heavy)
• any other broken driver (e.g. networking)
• disk space? (although crashing would be strange)

Whatever you are experiencing, you should experience with some alternative way of stressing out above components.

[onecable5781]

Right. If it was a stochastic random process, I would agree with you. This happens quite deterministically on my machine -- only with ortools install (I have installed GMP/mlpack/boost and other heavy libraries without any issues) and exactly at the step I have mentioned in the OP. That is why I asked if there was anything rather computationally expensive that was happening exactly after this step in the build process.

[StevenGay]

In your step 3, you are passing -j, which means "compile with maximum parallelism". Maybe you are getting out of memory? You could pass a -j 4 instead, to limit parallelism?

…

On Tue, Feb 11, 2025, 17:28 onecable5781 ***@***.***> wrote: Right. If it was a stochastic random process, I would agree with you. This happens quite deterministically on my machine -- only with ortools install (I have installed GMP/mlpack/boost and other heavy libraries without any issues) and exactly at the step I have mentioned in the OP. That is why I asked if there was anything rather computationally expensive that was happening exactly after this step in the build process. — Reply to this email directly, view it on GitHub <#4535 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEVHRIFSJQWGMWH26MQ6T6D2PIQMLAVCNFSM6AAAAABW5G2KQ2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJUGY3TMOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[onecable5781]

I am running it now with -j 2 just to be sure and I am indeed past 8% :-)

That command followed by

sudo cmake --build build --config Release --target install -v

Installs it. Thank you.