Process tries to allocate 133TB of memory
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.1k
- Forks
- 348
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
While processing the attached SVG file the process fails with the following error message:
`memory allocation of 133671936000000 bytes failed`
We know that limiting the memory allocation is already the topic of issue #815. But considering the scale of the allocated memory we thought that it might be interesting anyway.
Our team discovered the issue during a current research project focusing on the schema-based generation of test-data for different XML specification formats.
### Steps to Reproduce
1. Execute `resvg test.png
`
### Environment:
• OS: macOS 15.1.1
• reSVG version: 0.44.0
### SVG File:
```xml
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the attached SVG using `resvg test.png` on reSVG 0.44.0, then trace the rendering path responsible for the 133TB allocation. Compare the behavior with the memory-limiting work in issue #815; done means the input no longer attempts an extreme allocation and fails in a controlled way.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100