[TIMOB-5106] Kitchensink: Crash after continued use of Kitchensink
GitHub Issue | n/a |
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2011-10-13T11:10:23.000+0000 |
Affected Version/s | Release 1.8.0 |
Fix Version/s | Sprint 2011-42 |
Components | iOS |
Labels | kitchensink, regression |
Reporter | Eric Merriman |
Assignee | Sabil Rahim |
Created | 2011-08-24T15:35:22.000+0000 |
Updated | 2017-03-07T19:53:39.000+0000 |
Description
Description:
While testing Kitchensink, I started getting out of memory issues and experienced a crash shortly after. There was no log. A few hours later, I got a crash with a log. This may be difficult to reproduce and may be due to the architecture of the application. Logging for completeness. See attached crash log. Below find example of memory warnings prior to first crash:
Mon Aug 22 15:26:05 unknown UIKitApplication:com.appcelerator.titanium[0xfbf4][82] : [DEBUG] loading: /var/mobile/Applications/7A39CEBA-94DF-4299-B9D9-978EC89C50A5/KitchenSink.app/examples/table_views.js, resource: examples/table_views_js
Mon Aug 22 15:26:05 unknown configd[25] : jetsam: kernel memory event (91), free: 711, active: 1599, inactive: 1956, purgeable: 1655, wired: 9240
Mon Aug 22 15:26:05 unknown SpringBoard[28] : Received memory warning. Level=2
Mon Aug 22 15:26:05 unknown MobileMail[64] : Received memory warning. Level=2
Mon Aug 22 15:26:05 unknown KitchenSink[82] : Received memory warning. Level=2
Mon Aug 22 15:26:05 unknown UIKitApplication:com.appcelerator.titanium[0xfbf4][82] : [INFO] Due to memory conditions, 0 of 0 image cache entries were unloaded from cache.
Mon Aug 22 15:26:05 unknown MobileMusicPlayer[78] : Received memory warning. Level=2
Steps to reproduce:
1) Install KS 1.8.0 on iPod 3rd gen.
2) Begin tests
3) examine console output
4) Continue until application crashes
Result:
Eventual application crash, potential for out of memory condition and warnings.
Expected result:
The animation completes without additional images being displayed
Notes:
While crashes were experienced with 1.7.2, these occurred quicker, and with slightly higher frequency.
Attachments
This issue links to the same problem mentioned in timob-5449 , the fix for it is already in master. This occurs as callback's KrollContext already left before the KrollCallback had time to unregister itself.
Closing ticket as duplicate.