summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* [AM] Remove spurious warning for staged cleanup.wolfbeast2019-01-30-1/+1
| | | | This fixes #773.
* Increase slice time for longer running CCs.Andrew McCreight2019-01-29-3/+14
| | | | | | | | | If a CC takes too long (around 50 slices) or gets interrupted by a GC, we have to finish it synchronously, which can cause a big pause. This patch tries to avoid that by eagerly increasing the slice budget the longer a CC goes on. It linearly increases the slice time from 5ms to 40ms as we approach the halfway point of a CC (1 second), matching GC pauses, and then leaves it at 40ms.
* Increase purple limit triggers for CC.wolfbeast2019-01-29-2/+2
| | | | | Making these much larger to allow more purple buffer buildup and prevent overzealous cycle collection on purple buffer pressure.
* Merge branch 'master' into cycle_collector-workwolfbeast2019-01-29-323/+604
|\
| * Merge pull request #948 from trav90/media-workMoonchild2019-01-29-14/+49
| |\ | | | | | | Always treat composition time offsets as signed
| | * Always treat composition time offsets as signedtrav902019-01-28-14/+49
| | | | | | | | | | | | | | | Even for version 0 ctts atoms that technically should contain only unsigned values.
| * | Reduce number of allocations in AutoStopwatchDavid Teller2019-01-29-9/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes two related issues. 1. The AutoStopwatch uses a stack-allocated `mozilla::Vector` to communicate with its callback during each compartment switch. This vector was designed to allow its contents to be stack-allocated but they turned out to be accidentally heap-allocated. 2. During each tick, the stopwatch fills a vector `recentGroups_`. This vector always started with minimal capacity and had to grow repeatedly as groups were added, causing repeated reallocations. This patch preallocates `recentGroups_` to have the same capacity as the previous tick. We expect that this should eventually reach a stable size that closely matches the actual needs of the process.
| * | Revert "Reduce number of allocations in AutoStopwatch"wolfbeast2019-01-29-25/+11
| | | | | | | | | | | | This reverts commit 3476c1d60ec29c5497123194acd7a9310b1023d2.
| * | Reduce number of allocations in AutoStopwatchDavid Teller2019-01-28-11/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes two related issues. 1. The AutoStopwatch uses a stack-allocated `mozilla::Vector` to communicate with its callback during each compartment switch. This vector was designed to allow its contents to be stack-allocated but they turned out to be accidentally heap-allocated. 2. During each tick, the stopwatch fills a vector `recentGroups_`. This vector always started with minimal capacity and had to grow repeatedly as groups were added, causing repeated reallocations. This patch preallocates `recentGroups_` to have the same capacity as the previous tick. We expect that this should eventually reach a stable size that closely matches the actual needs of the process.
| * | [PALEMOON] Remove some dead code from browser gluewolfbeast2019-01-28-8/+0
| | | | | | | | | | | | (plugin update service)
| * | [BASILISK] Align browser glue with TychoAM for enableable add-ons.wolfbeast2019-01-28-20/+20
| | |
| * | Remove remote add-on debugging control.wolfbeast2019-01-28-14/+0
| | |
| * | Add nullcheck for addons (pre-installed webextensions return null)wolfbeast2019-01-28-2/+2
| |/ | | | | | | Tag #937.
| * Merge pull request #945 from FranklinDM/audioindicator-lwtheme-fixMoonchild2019-01-28-18/+18
| |\ | | | | | | Only use white audio indicator when using a lightweight theme
| | * Only use white audio indicator when using a lightweight theme [pinned tabs]FranklinDM2019-01-27-9/+9
| | |
| | * Only use white audio indicator when using a lightweight themeFranklinDM2019-01-26-9/+9
| | |
| * | Fix incorrect file reference in `onDownloadDragStart`wolfbeast2019-01-25-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Follow-up to Janek's port in 462332eee018e24d88255c708fa8acb67a717673 where this variable was changed creating a mismatch with surrounding code. This fixes #943.
| * | Fix bookmarks backup logic.wolfbeast2019-01-24-52/+36
| | | | | | | | | | | | | | | | | | | | | | | | This is a follow-up to an incomplete patch submitted to Tycho: https://github.com/MoonchildProductions/Pale-Moon/pull/1082 Also reduces the idle time before attempting to backup in the background to 10 minutes (was 15).
| * | [BASILISK] Disable WebEx support.wolfbeast2019-01-21-1/+1
| | |
| * | Check for contiguous buffer state.wolfbeast2019-01-21-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we are reading large image data (i.e.: people using webp to stream video instead of the native webm format; I'm looking at you, Giphy!) we can run into the situation where the available data is not in a contiguous buffer, and we need to either buffer additional data or re-buffer from the start. If we don't do this, we can run into issues because of buffer over-reading (causing corrupted data if allocated or more likely crashes if not allocated). Re-buffering is expensive, but this should be rare and limited to dealing with unintended use for animated image formats. This resolves #940.
| * | Make Sourcebuffer::AppendFromInputStream handle canceled image loads.wolfbeast2019-01-21-3/+11
| | |
| * | Make resuming of decoding work for anonymous decoders.wolfbeast2019-01-21-7/+18
| | |
| * | Update libwebp to version 1.0.2wolfbeast2019-01-21-173/+395
| | | | | | | | | | | | This resolves #939.
| * | Properly camelCase dom.intersectionObserver.enabled pref.wolfbeast2019-01-19-3/+3
| | |
| * | Revert "Disable IntersectionObserver API because of crashes."wolfbeast2019-01-19-2/+1
| | | | | | | | | | | | This reverts commit ac1beef5c10a114afe18897d5d3ced24ac378b92.
| * | Actually unlink targets from registered intersection observers.wolfbeast2019-01-19-0/+10
| | | | | | | | | | | | | | | | | | | | | When a node is released/removed, and it has an intersection observer attached to it, that observer should be unlinked at the time of release. This resolves #935.
| * | Disable IntersectionObserver API because of crashes.wolfbeast2019-01-19-1/+2
| | | | | | | | | | | | See #934 and #935.
* | | Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTSwolfbeast2019-01-18-119/+1
| | |
* | | Consolidate tracing and traversing.wolfbeast2019-01-18-16/+38
|/ /
* | Merge branch 'master' of https://github.com/MoonchildProductions/UXPwolfbeast2019-01-18-3/+30
|\ \
| * \ Merge pull request #931 from Ascrod/masterMoonchild2019-01-18-3/+30
| |\ \ | | | | | | | | Fix option for disabling HSTS in Pale Moon
| | * | Fix check for HSTS when service is disabled.Ascrod2019-01-17-1/+1
| | | |
| | * | [PALEMOON] Fix the option to disable HSTS.Ascrod2019-01-16-3/+3
| | | |
| | * | Add preference for fully disabling HSTS.Ascrod2019-01-16-0/+27
| | | |
* | | | Rewrite IntersectionObserver list handling to be more robust.wolfbeast2019-01-18-8/+40
|/ / / | | | | | | | | | Tag #935.
* | | Add isIntersecting property to IntersectionObserverEntry.wolfbeast2019-01-17-0/+11
| | | | | | | | | | | | | | | | | | Per updated spec. This resolves the issue raised in #249.
* | | New cycle version bumpwolfbeast2019-01-17-1/+1
| | |
* | | Improve toolbar icons for all DPIswolfbeast2019-01-17-2160/+3222
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tag #576. - Redraw toolbar SVG images, pixel-aligning them as best as possible with manual node placement on the pixel grid. - Reintroduce PNG versions for < 1.33 dppx (with added glow arrow) - Make the css adaptive around the 1.33 dppx border, using PNG below that threshold and SVG above it.
* | | [PALEMOON] Add captive portal preference to the UI.wolfbeast2019-01-16-0/+15
| | | | | | | | | | | | Tag #860
* | | Add matching browser.newtab.choice pref to prevent error.wolfbeast2019-01-16-0/+2
| | |
* | | [PALEMOON] Move Advanced prefs l10n strings to their proper placewolfbeast2019-01-16-6/+6
| | |
* | | [PALEMOON] Clean up advanced prefs XULwolfbeast2019-01-16-14/+0
|/ / | | | | | | | | Remove commented out old Firefox prefs that haven't been used in a loon while and aren't going to be reinstated.
* | [WebExAM] Use proper application name in WebExtension API error message.wolfbeast2019-01-14-1/+2
| |
* | Merge pull request #929 from adeshkp/remove-telemetry-stubsMoonchild2019-01-14-3443/+71
|\ \ | | | | | | Telemetry: Remove stubs and related code
| * | Make `AllowExperiments` return `false` as it is not useful without telemetryadeshkp2019-01-14-1/+4
| | |
| * | Remove a pointless `switch` after telemetry cleanupadeshkp2019-01-14-14/+0
| | |
| * | Remove unused telemetry timer from HTMLMediaElement.hadeshkp2019-01-14-7/+0
| | |
| * | Telemetry: Remove stubs and related codeadeshkp2019-01-12-3422/+68
|/ /
* | Update basilisk blocklist header.wolfbeast2019-01-09-1/+3
| |
* | Align Element.ScrollIntoView() with the spec.wolfbeast2019-01-08-25/+56
| | | | | | | | | | | | | | This also removes the (unused) shadow alias from nsIDOMHTMLElement which used the different calling convention. This resolves #927