Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

nim-lang / Nim Public

Notifications You must be signed in to change notification settings
Fork 1.5k
Star 16.9k

Code
Issues 2k
Pull requests 86
Actions
Projects 2
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

bugfix memory leak in parseJson() on invalid json-string#24686

Closed

ThomasTJdev wants to merge 4 commits intonim-lang:develnim-lang/Nim:develfrom ThomasTJdev:patch-2ThomasTJdev/Nim:patch-2Copy head branch name to clipboard

+42-19

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Feb 12, 2025

Explicit close stream after parseJson
ThomasTJdev
authored
Only go for closing the stream if it's not nil, otherwise valgrind complains
ThomasTJdev
authored
Clear newJObject() and newJArray() in case of bad parsing
ThomasTJdev
authored
remove GC calls and just assign to nil
ThomasTJdev
authored

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.