[TIMOB-2062] Android: Opening some windows has slowed considerably
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2012-08-22T12:09:14.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android |
Labels | tbs-1.8.0 |
Reporter | Thomas Huelbert |
Assignee | Neeraj Gupta |
Created | 2011-04-15T03:09:20.000+0000 |
Updated | 2017-03-10T18:23:27.000+0000 |
Description
g1 running 1.6 and the sim running 2.2 Ti Mobile sdk 1.5.0.02c264
1.baseUI>Window properties (baseUI>views>table
views>table view layout2)
2.publish in 1.5.0 and 1.4.1.1
3.time how long it takes from tap to when the buttons render
results: in 1.4.1.1 ~1 second. 1.5.0 ~2.5 seconds (timed manually)
1.5.1 to 1.6 RC1 the widow open time has slowed as will. Tested in emulator using KS on 1.5.1 and 1.6RC1.
Also identified by customer using device. Ticket reference: http://developer.appcelerator.com/helpdesk/view/72781">http://developer.appcelerator.com/helpdesk/view/72781
This is mostly a perception issue as to when "done" is. In the previous release it did some things partially and you saw something quicker, but it wasn't really done. Now to handle the create/start/resume event properly, we have to handle booting a js context and block on the main thread. All non-critical tasks should be moved into the
open
event so that the activity will load faster. There is no way for us to guess at what code can be delayed so the developer must do the work manually. In summary, do more stuff asynchronously via event, rather than all of it in the global scope.Tested on a Samsung Galaxy S2 using TiSDK 2.2.0v20120821095711, unable to reproduce the issue. Ticket marked as resolved.
Closing ticket as the issue cannot be reproduced.