Investigate OCC mesh construction SIGSEGV and union failures on detailed multilayer PCB copper
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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:
- Check clean current main and distinguish upstream behavior from defects introduced by the local experimental engine.
- 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.
- Prefer two stacked PRs: first the reproduction (visual geometry/mesh output where useful), then the fix on top.
- 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.
- 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分
- マージ済み PR(30日)
- 1
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
似ている issue
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
openclaw/openclaw#199885 · コメント 2 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
-
feature needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
BoardGamesEmpire/board-games-empire-backend#1306 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
sequant-io/sequant#1689 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100