If you still have the old config file, it would be great if you could find exactly which setting caused the issue, and if found, report it to the developers.
You could speed that up by first copying the top half of the old file to a new darktablerc, and see if that reproduces the crash. If yes, rename that file to ‘suspect’, and copy the top half to a new darktablerc. If the top half does not cause a problem, try the bottom half, and keep halving until you find the culprit line.
Of course, if updating darktable fixed the issue, there’s is no point. I don’t know if that’s what you meant with ‘an update managed to get it working’, because you also said you’d have to reconfigure everything.