Clean up memory leaks

Open
#54 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
22/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
backend

Research direction

The issue names no file, class or test, so start by locating the record-insertion path in the plugin's import job code and finding where exceptions can escape between the insert and the release of the record. The only comment is a single old reply, so treat the thread as unresolved context rather than a decision. Done means every insertion that throws leaves no record behind and a test reproduces the leak before the fix.

Written by the indexing model from the issue text.

Description

Defect

Looks like in some of the insertion, if an exception is thrown the record is not released

Dominant language
PHP
Stars
20
Forks
32
PR merge metrics
No merged PRs in 30d

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 omeka/plugin-CsvImport

All issues in omeka/plugin-CsvImport

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.