Date Picker Memory Usage

You must Login before you can answer or comment on any questions.

Hi All,

I am in the process of porting a multithreaded app into single threaded commonJS style app. Everything is going well and I am seeing both performance and memory improvements. I am using the xcode profiling tools to ensure the app is actually improving.

My app uses several date pickers (Ti.UI.createPicker({type : Ti.UI.PICKER_TYPE_DATE}). When I add these pickers to a view, each one seems to add a HUGE amount of memory. I'm talking like 2MB for each picker. I've gone through and definitively can say that it is the picker. I'd never noticed the picker memory usage before because it was hard to identify what was chewing it up in the old app architecture.

Anyone else seen this? Is this the expected memory usage?

I've tested on iOS5.1 and iOS6 using SDK 2.1.3RC2, results are identical, as is iOS5.1 with 2.1.2.

Nick

— asked 8 months ago by Nick The Geek
5 Comments

  • Doing further investigation doing a healshot analysis I can see that memory is indeed being used by the DatePicker with the usage in bunch of 'UISectionRowData refreshWithSection:tableView:tableViewRowData' under the object.

    — commented 8 months ago by Nick The Geek

  • Anyone?

    — commented 8 months ago by Nick The Geek

  • if it's still a problem, post an actual sample to replicate what you are seeing. I will follow up to walk through it to make sure the problem it's fixed already.

    — commented 7 months ago by Eduardo Gomez

  • Show 2 more comments

Your Answer

Think you can help? Login to answer this question!