1802852 - "The clearkey plugin has crashed" on Raspberry Pi 4 (4GB)

Status: RESOLVED DUPLICATE of bug 1761013

(Core :: Audio/Video: GMP, defect)

Description

[juraj.masiar]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

0. using Firefox 102.5.0esr (64-bit) on Raspberry Pi 4 using official 64bit OS
1. load page:
   https://reference.dashif.org/dash.js/latest/samples/drm/clearkey.html

Actual results:

Message "The clearkey plugin has crashed" will appear.
Crash report:
https://crash-stats.mozilla.org/report/index/71b99fba-b6b7-46f9-8e50-6994d0221128

Expected results:

I guess it shouldn't crash?

I've found a discussion about this on reddit:
https://www.reddit.com/r/firefox/comments/v4ywy1/the_notification_message_the_clearkey_plugin_has/

Comment 1

[juraj.masiar]

Attachment: Screenshot 2022-11-28 101640.png

Comment 2

[Negritas Sergiu, Desktop QA]

Hello! I have tried to reproduce the issue on with firefox 109.0a1(2022-12-02) on Ubuntu 22.04 but unfortunately I wasn't able to reproduce the issue on my end.
Could you please answer the following question in order to further investigate this issue?

1. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
2. Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
3. Do you have any addons installed if so can you list them?

Comment 3

[juraj.masiar]

Attachment: fresh new profile

Hello,

1. yes, it will crash also in the fresh new 102.5.0esr (64-bit) profile (see the new image)
2. I can't test it in Nightly, there are only ESR builds available for Raspberry Pi
3. fresh profile, so no addons

This bug may be ARM related, it would be nice if someone could test it on some other ARM device.

Comment 4

[Negritas Sergiu, Desktop QA]

Hello Juraj! Thank you for the reply, unfortunately we don't have an ARM device. I will mark this issue as QA-not-actionable and set a component for it. If it's not the right component please feel free to change it to an appropriate one.

Have a nice day!