Ticket #1051 (closed bug: fixed)

Opened 3 years ago

Last modified 2 years ago

Investigate empty layout block memory leak in 5.X player

Reported by: zach Owned by: pablo
Priority: Milestone: Player 5.7
Component: flash Keywords:
Cc: jeroen Forum thread: http://www.longtailvideo.com/support/forums/addons/using-and-creating-skins/14321/memory-leak-because-of-nacht-skin#comment-86538

Description

Skins without the <layout> section use linearly increasing amounts of memory and cause a cpu usage of 100% after some time. Profiling indicates lots of free sprite objects with the origin jwplayer.view.components:ControlbarComponent.

Change History

comment:1 Changed 3 years ago by zach

  • Component set to flash

comment:2 Changed 3 years ago by jeroen

  • Type changed from enhancement to bug

comment:3 Changed 3 years ago by zach

  • Milestone changed from Player 5.4 to Player 6.0

comment:4 Changed 2 years ago by pablo

  • Milestone changed from Player 6.0 to Backlog

Milestone Player 6.0 deleted

comment:5 Changed 2 years ago by jeroen

  • Milestone changed from Backlog to Player 5.7

Pushing this bug up. It seems like a significant problem when playing long-form content, and it also might not just be related to the empty layout block:

http://www.longtailvideo.com/support/forums/jw-player/servers-and-streaming/19061/

comment:6 Changed 2 years ago by jeroen

Here's another thread that may also be related. In fullscreen, JW Player uses 60% CPU even when idle:

http://www.longtailvideo.com/support/forums/jw-player/setup-issues-and-embedding/18558/

comment:7 Changed 2 years ago by pablo

  • Status changed from new to assigned

This should be fixed in [1782]. I'll leave this ticket open so we can gather some feedback.

comment:8 Changed 2 years ago by pablo

[1782] introduced an issue with the progress bar updating. This has been fixed in [1788].

comment:9 Changed 2 years ago by pablo

  • Status changed from assigned to closed
  • Resolution set to fixed

Checked in an additional fix ([1791]) to address possible memory leaks in state change and resize events in addition to time update events.

Note: See TracTickets for help on using tickets.