Closed Bug 1701388 Opened 3 years ago Closed 11 months ago

Addon Plasma Integration eats one DOMWorker constantly

Categories

(Core :: DOM: Workers, defect, P3)

Firefox 88
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: private_lock, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

Start FF 87 / 88 beta in clean fresh profile
enable profiler https://profiler.firefox.com/
install addon: https://addons.mozilla.org/de/firefox/addon/plasma-integration/
Version 1.8.0.1
run profiler for 10 sec

Actual results:

One DOM Worker is completely gone in setTimeout handler / js:RunScript
https://share.firefox.dev/2O1MA9U

Expected results:

This does not cause actual CPU load (observed by external Systemmonitor) - it just confuses the profiler / or is going to some processor-wait-state???

See also: bug 1700200 comment 3 and bug 1684139

Hi Holger!
I was not able to reproduce this issue on latest Nightly 89.0a1 (2023-03-31)(64-bit) on Ubuntu 20.04.
Please could you try to reproduce it on latest Nightly and tell us your input? You can download it from here: https://nightly.mozilla.org/.

I've just installed in a new profile the addon mentioned by you. I think that DOM Worker didn't experience any problems. This is the Firefox Profiler link:

https://profiler.firefox.com/public/9q36mtvvnr2w7bvgvtm7zkhhkv0wmx3gy5zpzb0/calltree/?globalTrackOrder=0-1-2-3-4-5-6-7&localTrackOrderByPid=44244-8-9-0-1-2-3-4-5-6-7~44367-0~44429-0~44500-1-0~44438-0~44694-0~44648-0~&thread=0&v=5

Flags: needinfo?(private_lock)

Well - I have no access to FF from 2023 :D

The link you posted does not load in FF 88beta - only in FF 89 nightly, though it claims to be recorded by FF 88.

It gets even better, when I record a profile of 89, it does not have a single DOMWorker
https://share.firefox.dev/3rEHmP4
So yes, for now, I conclude 89 is not affected, as it does not have DOMWorkers any more ???

But with FF 88 beta, the steps to reproduce work:
https://share.firefox.dev/3ds6gwp

OK ... the links open - this was my stupid fault ...

Anyway, I just got the notification, that 88 beta4 was replaced by 88 beta 5 ... getting this new profile:
https://share.firefox.dev/31yiiyr

There is a minor change: under js:Runscript the tree unfolds a little further to "loop" > "poll" - see screenshot.

Flags: needinfo?(private_lock)

I'll set a component to have a starting point of this. Please, if not the right component feel free to route this ticket to the corresponding team, thanks!

Component: Untriaged → DOM: Workers
Product: Firefox → Core
Severity: -- → S3
Priority: -- → P3

The DOM-Workers returned to the profile of FF89beta15 ... and the Add-on Plasma-Integration eats one of them continuously:
https://share.firefox.dev/3woFjBt

Well two years later and several upgrades, I'm now running the plasma integration without further issues - problem got magically solved :D

Status: UNCONFIRMED → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: