[TIMOB-3008] iOS: saw deadlock while toggling network - intermittent and not repro
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T02:00:40.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M08 |
| Components | iOS |
| Labels | deadlock, ios, network, regression, release-1.6.0, reported-1.6.0 |
| Reporter | Thomas Huelbert |
| Assignee | Blain Hamon |
| Created | 2011-04-15T03:34:39.000+0000 |
| Updated | 2011-04-17T02:00:40.000+0000 |
Description
Seen on a 4gt ipod running 4.1 only, not repro on same device, nor on others checked. logging in case crash log helps dev.
ipod touch 4GT (4.1) [INFO] Titanium SDK version: 1.6.0 (01/31/11 08:03 f9036ef).
1.Platform > network
2.Background app
3.settings > airplane mode turn it on
4.home button, tap app icon
resultds: deadlock occurred (as per the crash log, attached if LH lets me today).
okay no attachments today either... sigh, emailed to Blain and Stephen
(from [09db865ff9e57aa9a24854919b9670aa645923c4]) [#3008 state:fixed-in-qa] Try to accquire a lock instead of outright claiming it. We need to be much more careful about that with analytics in resume/suspend operations. https://github.com/appcelerator/titanium_mobile/commit/09db865ff9e57aa9a24854919b9670aa645923c4"> https://github.com/appcelerator/titanium_mobile/commit/09db865ff9e5...
REPO STEPS (based on crash log):
This one is going to be very tricky to duplicate. What happened was that while one of the suspend/shutdown/resume analytics events was occurring, a SECOND analytics event was then sent in the middle of the analytics request. So, this has to be timed just right:
This time period is probably measured in tenths (or less) of a second. One possible way to do this is to force an analytics event on the 'resume' notification sent by the app while on a slow network.
not seeing it, closing against [INFO] Titanium SDK version: 1.6.0 (02/02/11 07:59 a632082) need a better test case at some point.