{"push_id":1052771880,"size":7,"distinct_size":7,"ref":"refs/heads/AsyncSpawnFaultInjection","head":"3a936d1283612f058f91790f7fa874f4ac375ac5","before":"2e0fe91e295ed058a018cad58ca602338b4a7ff7","commits":[{"sha":"f8db1987cfd70f4071da552b364a7f4e64180050","author":{"email":"4a4cdc5116fb3eae8a810d7bf105917732448500@contextis.co.uk","name":"Jan Mitchell"},"message":"Adding fixes for two NULL pointer dereferences","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/f8db1987cfd70f4071da552b364a7f4e64180050"},{"sha":"81a01b1fd5736d5b7b1fb01657da20022067c48d","author":{"email":"196f7372942e93c00aefc70a600eb542e0d2cd1f@microsoft.com","name":"Suwei Chen"},"message":"OS4927797: TypeofElem fastpath mishandling out-of-range scenario\n\nFastpaths for opcode 'TypeofElem' mistakenly return 'number' for certain out-of-range situations.\nFix by adding check 'undefined' for return values in the fastpaths.","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/81a01b1fd5736d5b7b1fb01657da20022067c48d"},{"sha":"e4a75768d658c2d4a96afe674cf286853902f250","author":{"email":"196f7372942e93c00aefc70a600eb542e0d2cd1f@microsoft.com","name":"Suwei Chen"},"message":"[MERGE #729] OS4927797: TypeofElem fastpath mishandling out-of-range scenario\n\nMerge pull request #729 from suwc:build/suwc/bugfix\nFastpaths for opcode 'TypeofElem' mistakenly return 'number' for certain out-of-range situations.\nFix by adding check 'undefined' for return values in the fastpaths.","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/e4a75768d658c2d4a96afe674cf286853902f250"},{"sha":"f4eb3b0c9cc3bb8726b5792be56814f8e0d7f04e","author":{"email":"f978ae746fa455d6c7b8b056655b015ed0b134a7@microsoft.com","name":"Tom Care"},"message":"Class extends clause has different source locations between defer/non-defer parse modes\n\nTracked in OS 7030846.\n\nWhen emitting a class statement with an extends clause, we made the assumption that the start and end of the bytecode for that statement happened in the same place in defer and non-defer parse modes. In fact, it is possible to have the load happen in different locations, e.g. if we cache a previous load's register location in non-defer parse mode and have to load from a local slot in defer parse mode.\n\nThe fix is to set the statement location to the InitClass bytecode.","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/f4eb3b0c9cc3bb8726b5792be56814f8e0d7f04e"},{"sha":"e5eca9052feccaa117b7266b39b91dd5c56da604","author":{"email":"f978ae746fa455d6c7b8b056655b015ed0b134a7@microsoft.com","name":"Tom Care"},"message":"[MERGE #738] Class extends clause has different source locations between defer/non-defer parse modes\n\nMerge pull request #738 from tcare:classExtends\nTracked in OS 7030846.\n\nWhen emitting a class statement with an extends clause, we made the assumption that the start and end of the bytecode for that statement happened in the same place in defer and non-defer parse modes. In fact, it is possible to have the load happen in different locations, e.g. if we cache a previous load's register location in non-defer parse mode and have to load from a local slot in defer parse mode.\n\nThe fix is to set the statement location to the InitClass bytecode.","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/e5eca9052feccaa117b7266b39b91dd5c56da604"},{"sha":"eb834d772c3deae09c697897f920ef78321280df","author":{"email":"9202620134c02c2c59880ce77ca8d0dee6f50423@Microsoft.com","name":"Michael Ferris"},"message":"[MERGE #719] Adding fixes for two NULL pointer dereferences in asm.js","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/eb834d772c3deae09c697897f920ef78321280df"},{"sha":"3a936d1283612f058f91790f7fa874f4ac375ac5","author":{"email":"68302baa08cfb0bfbf8c275998759f15f7baddce@microsoft.com","name":"Taylor Woll"},"message":"Fix one use of JavascriptExceptionObject::GetThrownObject in the async spawn function which I missed during an earlier round of cleanup\n\nThis is fault-injection case which causes us to call a rejection handler\nwith nullptr instead of Javascript undefined value.\n\nAlso move TryRejectWithException calls out of catch handler","distinct":true,"url":"https://api.github.com/repos/boingoing/ChakraCore/commits/3a936d1283612f058f91790f7fa874f4ac375ac5"}]}