Chromium Blog: April 2012

Debugging Web Workers with Chrome Developer Tools

Monday, April 30, 2012

Web WorkersChrome Developer Toolsdedicatedshared

chrome://inspectdocumentationGoogle+discussion groupPosted by Yury Semikhatsky, Software Engineer

Fuzzing for Security

Thursday, April 26, 2012

fuzzingLKGR (Last Known Good Revision)

Managing test cases and infrastructure - To run at maximum capacity we need to generate a constant stream of test cases, distribute them across thousands of Chrome instances running on hundreds of virtual machines, and track the results.

Analyzing crashes - The only crashes we care about for security purposes are the exploitable ones. So we use Address Sanitizer to instrument our Chrome binaries and provide detailed reports on potentially exploitable crashes.

Minimizing test cases - Fuzzer test cases are often very large files—usually as much as several hundred kilobytes each. So we take the generated test cases and distill them down to the few, essential pieces that actually trigger the crash.

Identifying regressions - The first step in getting a crash fixed is figuring out where it is and who should fix it. So this phase tracks the crash down to the range of changes that introduced it.

Verifying fixes - In order to verify when a crash is actually fixed, which we run the open crash cases against each new LKGR build.

security principlesWebKitFFmpegPosted by Abhishek Arya and Cris Neckar, Chrome Security Team

Register now for the global Dart hackathon

Monday, April 16, 2012

North America:

Silicon Valley, California, USA

South America:

São Paulo, Brazil

Europe and Middle East:

London, England
Prague, Czech Republic
Tel Aviv, Israel

Asia:

Bacolod City, Philippines
Chandigarh, India
Goa, India
Karnataka, India
Manipal, India
New Delhi, India
Seoul, Korea
Tokyo, Japan

full list

Dart projectRegister today
Posted by Seth Ladd, Developer Advocate

Chrome’s WebRTC roadmap

Tuesday, April 10, 2012

preview WebRTCWhat's in:JSEPJSEPJavascript libTopologiesICE / STUN / TURNICE and STUNDTLS-SRTP DTLS-SRTPVP8, iSAC, iLBC, G.711What’s next?

Data API. Implementation will start once the network stack is ready.

Screen sharing.

PeerConnection proxying. The ability to relay a stream to a third party will not make our first version.

Recording. MediaRecorder specification work has not been completed yet.

discussion listPosted by Serge Lachapelle, Product Manager

Dec	JAN	Feb
	13
2020	2021	2022

Chromium Blog

Debugging Web Workers with Chrome Developer Tools

Fuzzing for Security

Register now for the global Dart hackathon

Chrome’s WebRTC roadmap

Labels

Archive

Feed