hurda
hurda
And contrary to 3.1.0, there's no console-message saying that lzma is being used, not even with `-v`.
> 2) this is the same behaviour as 3.0.10 but it's printing a message about it now. I enabled lzma secondary compression by default last release. Compression cannot be disabled...
My issue with `-P` 16MiB goes away when I define the compression-level with `-0`. I guess I'm hitting the virtual-memory-limit much easier with 3.1.0 than with 3.0.x.
Patching it on a Win7 64bit machine using both 32bit and 64bit executables works for me. ``` >xdelta3-3.0.11-i686.exe -dfv -s Mooncrat.rbx mooncrat_EU.patch foobar.rbx xdelta3: source Mooncrat.rbx source size 17.2 MiB...
Has the user tried checking the machine with memtest? Once I had a case of unexplainable crashes and errors of a single program on a single machine turning out to...
Great to hear that you're joining forces to move this addon forward.
Is it safe to switch to Brief now? Safe in the sense of the database and the state of feeds (unread items etc.) being accepted by the latest Brief-version.
Thanks.
Code of 1.6.2 ``` constructTooltip: function Brief_constructTooltip() { let bundle = document.getElementById('brief-bundle'); let rows = document.getElementById('brief-tooltip-rows'); let tooltip = document.getElementById('brief-tooltip'); // Integer prefs are longs while Date is a long...