I am not sure.
The only time I have seen such a crash was when using a local version of POM that tried to perform some of the calculations on the CustomUVs and then it only seemed to happen when using pixel depth offset. But I have never seen it with the vanilla POM node. Maybe some strange driver combo??
Does it happen with Pixel Depth Offset disabled? If not, does it happen when “Manual Texture Size” is set to true?
Also which version are you using? last suggestion is a longshot, but maybe you have the old version that failed to compile on macs. If the custom node inside of the POM has a line “int i;” try making it say int i = 0;