Tue, 06 Jan 2015 21:39:09 +0100
Conditionally force memory storage according to privacy.thirdparty.isolate;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
michael@0 | 1 | Open project list for further development: |
michael@0 | 2 | |
michael@0 | 3 | libvorbis: |
michael@0 | 4 | |
michael@0 | 5 | Meaningful error code returns |
michael@0 | 6 | |
michael@0 | 7 | still some padding at EOS |
michael@0 | 8 | |
michael@0 | 9 | Option for brute-forcing vq search on maptype 2 (helps on undertrained |
michael@0 | 10 | sets). |
michael@0 | 11 | |
michael@0 | 12 | encoder switch interface for binary compat through changes; ioctl()-like? |
michael@0 | 13 | |
michael@0 | 14 | API changes: |
michael@0 | 15 | break up some of the more monolithic calls (eg, allow access |
michael@0 | 16 | to MDCT domain data, additional low level framing capability) |
michael@0 | 17 | convenience calls for text comments |
michael@0 | 18 | |
michael@0 | 19 | other: |
michael@0 | 20 | |
michael@0 | 21 | command line suite |
michael@0 | 22 | 'crashme' |