Files
ResInsight/ApplicationLibCode/ReservoirDataModel
Magne Sjaastad 561bb35bd5 #14704 Guard against zero time-step count in findOrLoadKnownScalarResultForTimeStep
The bounds check on timeStepIndex was only applied when timeStepCount
was greater than zero. When a DYNAMIC_NATIVE result has zero known
time steps for a case, the check was skipped entirely and the
function still returned scalarResultIndex as valid, even though
m_cellScalarResults for it was never resized. Callers such as
RigSoilResultCalculator::calculate then indexed it out of bounds via
a CAF_ASSERT-only check (a no-op in Release builds), causing a
segfault.
2026-09-08 13:14:24 +02:00
..
2025-05-19 17:40:39 +02:00
2025-05-19 17:40:39 +02:00
2023-09-19 18:03:36 +02:00
2023-09-19 18:03:36 +02:00
2025-08-27 14:22:11 +02:00
2025-12-20 09:50:51 +01:00
2022-11-17 15:51:01 +01:00
2021-05-20 07:37:55 +02:00