Investigate OCC mesh construction SIGSEGV and union failures on detailed multilayer PCB copper

未关闭
#20 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by checking the clean current main branch against the captured engine base commit and local patch; the issue does not name source files or tests. Then reduce the failure to TSX rendered through core, preserving copper, capacitor contacts, ports, and material interfaces. Done means a bounded native regression reproduces and verifies conforming mesh output or an actionable diagnostic, with a resource-bounded board rerun.

由索引模型根据 Issue 内容生成。

描述

Problem

Detailed multilayer PCB meshing is blocking DDR signal-integrity validation. Native Gmsh/OpenCASCADE CAD construction fails before a tetrahedral mesh is produced, so Palace never runs.

Scope: this was observed in a task-local modified simulate-return-current engine based on commit aece592843df702ca4830d8b5556ce5cb3e17e1f. It has not yet been reproduced on clean current main. The failing experiment includes local material-tiling/passive-capacitor changes; this report does not establish a regression in a released package or a root cause in Gmsh itself.

Board context: https://tscircuit.com/0hmX/am3352-ddr-track-a-local-dfm-wip-20261007

Captured failure

The literal-copper common D5 experiment has 3,183 positive material cells and 24 physical ports, including 22 passive-capacitor ports. Geometry is partitioned per z interval before conforming shared material interfaces and ports.

Environment recorded by the experiment:

  • Linux x86_64 native runtime.
  • Gmsh 4.14.1 / OpenCASCADE 7.8.1.
  • Engine base commit: aece592843df702ca4830d8b5556ce5cb3e17e1f.
  • Local engine patch SHA-256: 2d18472ce5e4b6225ec6ad9521100d9041bd901b19cbe9fd4a4c0f3189d95f04.
  • Input model SHA-256: 651a32347c167911414aa3695857b8d6ebb3865d4f279d698c82caf674a3c5a6.
  • Original board SHA-256: 4ed4c784f20a492ac5736e026cdc62ce9ed35da8656c6f70c9132ef3be7e9700.
  • Captured process exit: 139 / SIGSEGV (signal 11).
  • Elapsed time: 327.73 s.
  • Maximum RSS: 9,258,204 KiB; address-space limit: 10,000,000 KiB; timeout: 900 s.

Last progress record and termination:

{"stage":"fragment_shared_material_interfaces_and_ports","seconds":61.999506363645196,"materialVolumes":3183,"ports":24}
timeout: the monitored command dumped core
Command terminated by signal 11

The launcher's separately captured exit code is authoritative. GNU time also printed a trailing Exit status: 0 despite its signal-11 report; this must not be mistaken for a successful mesh.

A separate, earlier CAD representation also failed with:

Union failed - BOPAlgo_AlertIntersectionFailed

Another partitioned attempt timed out after 900 s at fragment_air_materials_ports, with 1,685 copper volumes / 7 dielectric volumes / 19 ports and maximum RSS 9,320,312 KiB. These are different attempts; they should not be combined into a single purported stack trace.

Expected behavior

Native TSX-generated PCB geometry should produce a conforming mesh with correct material boundaries, physical ports and copper-interface ownership, or fail with an actionable geometry/resource diagnostic. A native crash or unbounded CAD Boolean stage prevents reliable simulation.

Reproduction and fix work

The captured board experiment is evidence, not yet a portable minimal reproduction. A separate coding task will:

  1. Check clean current main and distinguish upstream behavior from defects introduced by the local experimental engine.
  2. Reduce the failing case to actual TSX source rendered through core, including the new simulation elements. Generated Circuit JSON may be an output, but do not author/import a hand-written Circuit JSON fixture.
  3. Prefer two stacked PRs: first the reproduction (visual geometry/mesh output where useful), then the fix on top.
  4. Preserve physical copper, real ground returns, capacitor contacts, ports and material interfaces. Do not make the test pass by deleting difficult geometry, weakening checks, or silently changing the physical model.
  5. Add bounded regression coverage and diagnostics; verify a small native fixture before a resource-bounded board-case rerun.

Working hypothesis and limits

The failure location implicates CAD interface/Boolean construction on detailed copper. High memory use is observed, but the evidence does not establish whether the cause is an address-space allocation failure, a geometric degeneracy, or another OCC failure. Obtain a reduced reproduction and suitable native diagnostics before claiming the cause.

No accepted board field solution, DDR eye, or DDR pass/fail conclusion exists from these failed runs.

主要语言
TypeScript
星标
0
派生
0
平均合并
16 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。