TPEPlatform/2014-02-06

Streaming Media

• RTSP / bechen
  • bug 964209 - [RTSP] Content process crash after bug 959861
    • push try
  • bug 964132 - [RTSP] fix the cycle reference in RtpsMediaResource
    • Landed

Media Recording

• bug 968109 - [MediaRecorder] Support recording media stream from OfflineAudioContext
  • It seems use the OfflineAudioContext.

• bug 963481 - [Media Recorder] Implement MediaRecorder Constrainable Properties
  • Discuss with roc and feedback on w3c mail list. This feature required if application need to use another audio format.

• GUM
  • bug 952232 - [B2G][API Mediarecorder] "OnError" is not fired up in logcat when receiving/answering a phone call while media is recording / bechen
    • keep the ErrorCallback alive then fire "OnError" message

Graphics

• bug 945082 - lockscreen fade-out animation is still < 60fps /Jerry
  • Add more condition for temp surface
    • Still get failed from try server.
  • Add layer border to show temp surface usage
    • Review+
  • Fix the buffer size for scaling animation
    • Get better performance
  • re-compose the container layer if it has dirty region
    • Come from Matt. We get a boost performance improvement.

• bug 963917 - Gallery app high memory usage during 1st launch /Jerry
  • Release the canvans buffer explicitly.
    • Wait for the feedback.

• bug 959089 - Separate GrallocBuffer allocations from Compositor thread / Chiajung
  • Cleaning up WIP and starting to implement as a top level protocol

• bug 959487 - [MediaEncoder] Crash at imageclient when using MediaEncoder / Peter
  • Write the patch to improve the buffer lifecycle for video frame

• ScreenRecorder (LayerStreaming) / Peter
  • https://docs.google.com/a/mozilla.com/document/d/1Ae4K6FzVZUzboqZ5ofGfdbU3CJlHZdQCdpHPoy1ar6s/edit#heading=h.nxygpl97ske1
  • Prepare the diagram

• Memory report / Solomon
  • Modification to GFX relative memory reporter (gfxMemoryImageReporter/ SurfaceMemoryReporter/ Gralloc): Tried to convert the design from counter based to travesal based, such that the user can get the further detailed memory consumption data relative to image/texture...etc, instead of a simple total number.
  • Study the design of firefox profiler, to see if we can leverage the implementation data collection with timestamp:
    • Current memory report doesn't provide any temporal data. If we can record the memory usage variation during observation, we can see the how memory consumption changes along with time, or realize the reason why OOM killer kicks at a specific time.
    • Look into the way how firefox profiler generate data, to see if we can generate similar data, then we can use Cleopetra to present the memory consumption data

Input

• bug 955987 - [Text Selection] Change selection status in FrameScript /vilin
  • WIP is uploaded.
  • Implement a touchCaret handler for "touchmove" event in TabChild.
    • touchCaret is draggable and moving along with caret.
    • Text boundary are considered.
  • Need more test before being reviewed finally.