This is a friendly warning that your web-browser does not currently protecting your privacy and/or security as well as you might want. Click on this message to see more information about the issue(s) that were detected. November 21st, 2018 Bug­Id release 2018-11-21

Bug­Id release 2018-11-21

Download the official release .zip here.

Notable changes in this release

  • Bug ids for Access Violation exceptions have been standardized to the following format: <bug type id>:<memory details>[<size>][<offset>]. This includes bug ids for guard page access exceptions, as STATUS_­GUARD_­PAGE_­VIOLATION exceptions are just a sub-type of STATUS_­ACCESS_­VIOLATION. bug type ids W2RO and DEP have been changed back to AVW and AVE to simplify things.
  • Text descriptions for Access Violation exceptions should now all follow the same format.
  • Determining if an Access Violations happened near the stack is now more precise by relying on the actual virtual allocation for the stack to determine what memory range is part of the stack.
  • Determining the integrity level of a process was throwing unpredictable exceptions. Since I do not care much about this information and have little time to fix it, I've opted to disable the code and not put the integrity level in the report anymore.

Internal changes

  • I've renamed more time related variables to include "In­Seconds" in the name.
  • Test coverage has been improved by allowing you to trigger Access Violations in memory regions with specific properties (i.e. unallocated memory, reserved memory, inaccessible memory, and guard pages). Tests have been rebuild with VS 2017 and latest Win 10 SDK.
© Copyright 2019 by Sky­Lined. Last updated on September 9th, 2019. Creative Commons License This work is licensed under a Creative Commons Attribution-Non‑Commercial 4.0 International License. If you find this web-site useful and would like to make a donation, you can send bitcoin to 183yyxa9s1s1f7JBp­PHPmz­Q346y91Rx5DX.