Cheers, when using a small test design, precheck continues till the end, despite reporting Magic DRC violations. The design passes the local prefetch and passes even precheck and tapeout in the Efabless workspace. Nevertheless, with a large design, precheck works endlessly and finally stalls, when converting 670MB of Magic DRC violations into the xml report version. But I'm more interested in the subsequent steps. The swap space is 150G (for some reasons XOR needs it, but this is another issue). Is there a convenient way to skip Magic DRC during precheck, as it might be redundant anyway ? Thanks a lot for your answer in advance.

Sounds like your problem might be with sram DRC. For the standard sram magic drc, the actual layout is swapped with a lef version for drc. If you're using non standard sram, you might have to change the setup to do the same thing.

Thanks Mitch for your reply. The problem is not, that I have DRC violations. The point is, that in the last 6 hours only the precheck python script is running (at 15% performance) and the precheck python script then stalls after 6 hours. It leaves with an empty (but existing) drc check xml file. I assume it postprocesss the Magic DRC report and stalls.