Jump to content

Drag0nR3b0rn

Level 1
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Drag0nR3b0rn

Profile Information

  • Subscription
    PREMIUM
  1. I find it quite hard to accept that you either have to be a couple months behind, or to expose yourself to malicious addons by disabling the signing requirement. There should be another way.
  2. Doesn't work with firefox 41.0b1 on Mint Linux x64, because the xpi isn't signed. Could you please upload a signed xpi? Thanks.
  3. As much as I can see (using about:memory) the problem is that the web clipper creates three windows, event targets & event listeners per tab (whatever the tab is loaded or not), and causing a lot of heap allocations [that do seem like a mem leak of sorts] along the way. The CPU usage climbs peaks to 100% in three cases - on initial launch, on oppening a new tab and when another mem allocation occurs and firefox pages out (which happens quite a lot - as I see a mem usage increase of about ~6GB after enabling the web clipper). Edit: Here is a Firefox memory report, after enabling the web
×
×
  • Create New...