Modify ↓
Ticket #10381 (closed bug: invalid)
Inlcuding jQuery into Firefox extension growing up CPU load
| Reported by: | andrii.gakhov@… | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | misc | Version: | 1.6.4 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
jQuery 1.6.4, Firefox 7 (and Firefox 6), Ubuntu 11.04
When I am installing a Firefox extension which includes jQuery 1.6.4 (and does nothing) the CPU load of firefox growing up (from 1-3% to 7-9%). I noticed that the issue not occurred in jQuery 1.4
To illustrate the problem I've created a minimal example - 3 "empty" extensions for Firefox ( http://www.gakhov.info/resources/bugs/jquery_bug_extensions.zip) with/without jQuery
- extension without any jQuery (firefox CPU 1-3%) - OK
- extension with jQuery 1.4 (firefox CPU 1-3%) - OK
- extension with jQuery 1.6.4 (firefox CPU 7-9%) - PROBLEM
To reproduce the issue (using my minimal examples):
- Install extension_with_nothing.xpi extension ( http://www.gakhov.info/resources/bugs/extension_with_nothing.xpi)
- Restart Firefox
- Check top utility for CPU load (starts with 50% and stabilized on 1-3% CPU)
- Remove extension_with_nothing.xpi extension
- Restart Firefox
- Install extension_with_jquery_1.4.xpi extension ( http://www.gakhov.info/resources/bugs/extension_with_jquery_1.4.xpi)
- Restart Firefox
- Check top utility for CPU load (starts with 50% and stabilized on 1-3% CPU)
- Remove extension_with_jquery_1.4.xpi extension
- Restart Firefox
- Install extension_with_jquery_1.6.4.xpi extension ( http://www.gakhov.info/resources/bugs/extension_with_jquery_1.6.4.xpi)
- Restart Firefox
- Check top utility for CPU load (starts with 50% and stabilized on 7-9% CPU)
- Remove extension_with_jquery_1.6.4.xpi extension
- Restart Firefox
Why CPU load is increasing just because I include the jQuery 1.6.4?
Change History
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Note: See
TracTickets for help on using
tickets.

I don't think we'll be able to devote resources to investigating CPU load in firefox extensions, but jQuery does not take any CPU once it has been loaded, so if there is a problem, it is likely in firefox.