[TIMOB-2234] iOS: Opening files does not release vnodes
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2017-06-05T21:08:08.000+0000 |
| Affected Version/s | Release 1.5.0 |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | n/a |
| Reporter | Stephen Tramer |
| Assignee | Ingo Muschenetz |
| Created | 2011-04-15T03:14:22.000+0000 |
| Updated | 2017-06-05T21:08:08.000+0000 |
Description
Files which we open never have their vnodes cleaned up. Could be an Apple bug. Only a problem when opening ~1250 vnodes; this seems to be the iPhone's limit on the vnode table.
Should've clarified; this may only affect Ti.UI.imageView.image, and other image caching.
Some research has indicated that the issue may actually be URL->file translations since these use lstat(). Opening images off the filesystem uses open/fstat/close, meaning that vnodes and file descriptors are probably freed up (and testing outside Titanium bears this out, as it does not appear to have vnode problems).
However lstat alone does not account for the vnode issue. 273 vnode entries are unaccounted for by the sample program (provided by helpdesk, see #2014). Must be missing something.
Bumping to medium priority. This only affects opening 900+ files. The original HD ticket which brought this bug to my attention has switched to a non-local strategy, lowering the urgency of solving this bug.
System resource problem that's potentially related to either (a) memory or (b) iOS or even (c) both. Complex to solve and probably for 1.6.0.
Closing ticket due to the time passed and lack of progress over the past few years.