[TIMOB-1992] IOS: Strange behavior and intermittant mem leak on embedded video test case
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:57:45.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 |
| Components | iOS |
| Labels | defect, ios, regression, video |
| Reporter | Thomas Huelbert |
| Assignee | Blain Hamon |
| Created | 2011-04-15T03:07:35.000+0000 |
| Updated | 2011-04-17T01:57:45.000+0000 |
Description
1.Phone>Play Movie>embedded video
2.tap the small videos ful screen control
3.tap the screen to show video controls
4.tap done.
5.repeat.
6.repeast in simulator with instruments
results: I intermittantly had some strange videon behavior, with
multple alerts "mobie completed", once the video played on the
wrong screen
Results in instruments: out of 5 tries, twice I saw a mem leak
witht he folllowing information:
Leaked Object # Address Size Responsible Library Responsible
Frame
Malloc 32 Bytes 0xb43cb70 32 AudioToolbox
SimAggregateDevice::SimAggregateDevice(CFString
const*, CFString const, long&)
Malloc 32 Bytes 0xb43cab0 32 AudioToolbox
SimAggregateDevice::SimAggregateDevice(__CFString const,
CFString const*, long&)
NSCFDictionary
0xb43ca50 48 AudioToolbox
SimAggregateDevice::SimAggregateDevice(CFString
const*, CFString const, long&)
Malloc 48 Bytes 0xb4320e0 48 AudioToolbox
APComponent::CreateDispatchTable(AudioComponentPlugInInterface,
unsigned long)
That last change was a mistake on my part. Missed the second half of the description about the intermittent problems. But the memory leaks probably are the same as #1997 - which are confirmed to not be intrinsic.
The memory leaks aren't our fault (see #1997). However I am seeing duplicate alerts for 'embedded', but only under 4.2 - we should wait for 4.2GM to do a bunch of video testing, because it looks like there were a lot of changes to the system (again).
No longer able to reproduce. Marking fixed-in-qa; duplicate completed messages probably handled by another bug.
1.5.0.fb4b340 4gt ipod touch 4.2