Ruby ReportDatabase merging can lead to internal error

[Scafir]

Hello,

I'm now using the new ReportDatabase merge function. It seems to work well when merging small reports together, but I have seen it crash a few times now on larger reports when saving with:

ERROR: ../../../src/rdb/rdb/rdb.cc,737,cell != 0
ERROR: RuntimeError: Internal error: ../../../src/rdb/rdb/rdb.cc:737 cell != 0 was not true in ReportDatabase::save
  merge_internal_error.rb:8:in 'RBA::ReportDatabase#save'
  merge_internal_error.rb:8:in '<main>'

You can find a reporoducer in this zip file, simply uncompress it and run klayout -b -r merge_internal_error.rb

merge_internal_error.zip

Thank you!

[klayoutmatthias]

Thanks for the nice test case and for the bug report. The solution is under way ...

Problem wasn't size, but a cell mapping issue - when you merge RDB's with less cells into one with all cells, the problem does not happen.

I just wonder why the density error db is so huge - maybe the "marker" is a copy of the hierarchical chip boundary layer? In that case, "merged" should reduce it to a single rectangle.

[Scafir]

Hey! That's great to hear, thank you.

The huge report database came from the original gf180 code reporting density issues on every single polygon of the affected layer (metal1.output(...)), which is not very efficient to say the least. This has now been corrected to just reporting it once, as you suggested