margelo / margelo/react-native-fast-tflite
Release memory after running model and incorrect output array order
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 92
- Avg merge
- 13h 9m
- Merged PRs (30d)
- 2
Description
Thanks so much for this amazing lib! Couple questions:
- When I run a model, it doesn't seem to free up the memory it used. Is that supposed to happen automatically or do I have to free it up manually?
- After the run, the output arrays don't match the expected order as I see in Netron or when I run on python on my computer. I have to find the right index by looping through the model.outputs[i].name's, finding the one I want, and using that index in the model output (thankfully they have the same order). Is that normal?
Really appreciate the help and happy to send over any info you might need.
Contributor guide
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
No files, tests, or entry points are named. Start by clarifying whether the report concerns memory ownership, output ordering, or both, then identify the relevant model execution and output-mapping paths and define reproductions for each reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, tensorflow, typescript
- Domain
- machine-learning, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100