[bug] Gerber file parsing failed, the software froze, and memory usage reached 100%.

Open
  • Is something wrong?
#2,521 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
backend

Research direction

Start by extracting the uploaded Gerber samples and reproducing the import with default settings in KLayout v0.30.7 on Windows. Compare the two samples, including the .art file, and identify whether parsing causes the freeze and memory growth. Done means the files import without runaway memory use and the reported .art extension is supported or its limitation is clarified.

Written by the indexing model from the issue text.

Description

Gerber file parsing failed, the software froze, and memory usage reached 100%.

1.environment
klayout v0.30.7
windows 10 x64
The PC memory size is 48GB

2.read bailu-22sites drill2-3.gbr
Image

Image Image

All parameters are set to default values. Finally, click "Import".
The software may freeze, Windows memory usage may continuously increase, and Gerber files may fail to parse correctly.

3.I have uploaded the Gerber file; please unzip it.
https://github.com/libaineu2004/myepolltest/releases/download/Memory100percent/Memory100percent.rar

4.Additionally, klayout does not support Gerber files with the *.art extension. I have also uploaded a sample file here.
https://github.com/libaineu2004/myepolltest/releases/download/Memory100percent/art.rar

Dominant language
C++
Stars
1.2k
Forks
305
Avg merge
3d 2h
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KLayout/klayout

All issues in KLayout/klayout

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.