The underlying BEAM code (on Unix-ish systems, anyways) always calls utime with a not-NULL pointer:
but that’s been in the code for years and years, so it can’t be the reason for the recent change in behavior you observed.
The name of the function that’s calling touch (each_cycle) suggests that something may have changed in the dependency graph of your application. Comparing the output of mix xref between an older “known good” version and now could provide some insight.






















