https://github.com/mozilla-servo/libwapcaplet/commit/1c3343639571d65bc0c45cab8253dabe33aace9e
introduced locking in libwapcaplet (in October 2012, by Brian Anderson). Does
anyone remember
why this was necessary?
rust_lwc_lock calls pthread_mutex_lock
lwc_string_ref calls rust_lwc_lock
rust_lwc_st
Servo can now run some of tests in Official W3C CSS Test Suites.
http://www.w3.org/Style/CSS/Test/
For example, clear-001, 002, 003, 005 pass, and clear-004 fails because of
paint order (#677).
I would like to integrate passing tests to Servo. What would be the best way
to do so?
Servo memory usage steadily climbs when zooming in and out. This happens on
at least Linux and Android, and on Android, Servo is eventually killed by OOM.
Memory usage can be checked by /proc/PID/status, or smem on Linux and
showmap on Android.
To reproduce:
$ ./servo ../src/test/html/about-mozil
> I'm proposing we stagger the meetings. Every other week we'd meet at
> 5pm Pacfifc / 00:00 UTC, which is 9am in Seoul.
>
> 1) Would the North American contributors be ok with this semi-weekly time
> shift?
> 2) Would the Samsung developers be able to meet at 9am every other Monday?
This works f
4 matches
Mail list logo