Opened 2 years ago

Last modified 4 weeks ago

#13622 assigned bug

[MediaPlayer] media extractor thread uses 100% cpu

Reported by: diver Owned by: leavengood
Priority: normal Milestone: Unscheduled
Component: Applications/MediaPlayer Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #13928
Has a Patch: no Platform: x86-64

Description

hrev51305 x86_64

http://podtrac.com/pts/redirect.mp3/latenightlinux.com/media/LNL15.ogg

Playing this file is either makes MediaPlayer (media extractor thread) use 100% cpu or quits with:

pure virtual method called
terminate called without an active exception

Change History (9)

comment:1 by korli, 2 years ago

What about hrev51306?

comment:2 by diver, 2 years ago

CPU usage is still high. Can't trigger the crash tho.

comment:3 by korli, 2 years ago

https://dev.haiku-os.org/attachment/ticket/13410/VanillaFudge.mp3 seems to also be affected. MediaPlayer (or something it calls) seems to insist on extracting video frames which are not present.

comment:4 by vidrep, 2 years ago

Note that the the slider of the progress bar never moves while playing that ogg sample clip. I also see that problem with one of my m2ts trailers.

Last edited 2 years ago by vidrep (previous) (diff)

comment:5 by diver, 21 months ago

Blocking: 13928 added

comment:6 by waddlesplash, 12 months ago

High CPU usage fixed in hrev52358; however, the time indicator still does not increment on these files.

comment:7 by pulkomandy, 8 months ago

Still getting high CPU usage on some files here. In media player, "event queue runner", "playback manager", "media extractor thread" and "frame generator" threads are busy, as well as the main window thread.

How did we end up with so many threads just to play a media file anyway?

comment:8 by korli, 5 months ago

Owner: changed from korli to nobody
Status: newassigned

comment:9 by leavengood, 4 weeks ago

Component: Kits/Media KitApplications/MediaPlayer
Owner: changed from nobody to leavengood

Probably more of a MediaPlayer bug than Media Kit, though I don't know for sure yet. Probably the same issue as #15220.

Note: See TracTickets for help on using tickets.