Time travel debugging for browser components
US-2016292061-A1 · Oct 6, 2016 · US
US10268567B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10268567-B2 |
| Application number | US-201715485458-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 12, 2017 |
| Priority date | Apr 12, 2017 |
| Publication date | Apr 23, 2019 |
| Grant date | Apr 23, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems, methods, and computer-readable media are disclosed for using managed runtime environment semantics to optimize record and replay frameworks. One method includes: executing, by the computing system, a managed runtime component; interacting, by the computing system, with another system during the execution of the managed runtime component; determining, by the computing system, whether a non-deterministic event is to be logged in event logs during the execution of the managed runtime component; determining, by the computing system when the non-deterministic event is to be logged, whether semantics of the non-deterministic event to be logged includes a predetermined semantic, wherein the predetermined semantic includes one or more of optimistic zero copy actions; and logging, by the computing system when the semantics of the non-deterministic event includes the predetermined semantic, a copy of contents of the non-deterministic event in event logs during the execution of the managed runtime component.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for using managed runtime environment semantics to optimize record and replay frameworks, the method comprising: executing, by a computing system, a managed runtime component; interacting, by the computing system, with another system during the execution of the managed runtime component; determining, by the computing system, whether a non-deterministic event is to be logged in event logs during the execution of the managed runtime component; determining, by the computing system when the non-deterministic event is to be logged, whether semantics of the non-deterministic event to be logged include a predetermined semantic, wherein the predetermined semantic includes one or more of optimistic zero copy actions; and logging, by the computing system when the semantics of the non-deterministic event include the predetermined semantic, a copy of contents of the non-deterministic event in the event logs during the execution of the managed runtime component. 2. The method according to claim 1 , wherein the one or more of optimistic zero copy actions includes an immutable semantic pointer save. 3. The method according to claim 1 , wherein the one or more of optimistic zero copy actions includes a copy-on-write (“COW”) semantic pointer save. 4. The method according to claim 1 , wherein when the non-deterministic event having the semantics that include the one or more optimistic zero copy actions is on demand, values of the contents of the non-deterministic event are, on demand, copied into the event logs for storage or transmission. 5. The method according to claim 1 , further comprising: recording, by the computing system, a sequence of snapshots of the managed runtime environment during the execution of the managed runtime component. 6. The method according to claim 5 , further comprising: performing, by the computing system, time travel debugging by replaying at least a portion of the execution of the managed runtime component based at least in part on a snapshot from the sequence of snapshots and at least a portion of the event logs. 7. The method according to claim 5 , further comprising: performing, by the computing system, automated failure root-cause analysis by replaying at least a portion of the execution of the managed runtime component based at least in part on a snapshot from the sequence of snapshots and at least a portion of the event logs. 8. The method according to claim 5 , further comprising: performing, by the computing system, memory use analysis by replaying at least a portion of the execution of the managed runtime component based at least in part on a snapshot from the sequence of snapshots and at least a portion of the event logs. 9. A computing system for using managed runtime environment semantics to optimize record and replay frameworks, the system comprising: at least one processor; and memory comprising a managed runtime environment executable by the at least one processor, wherein the managed runtime environment, when executed by the at least one processor: executes a managed runtime component; interacts with another system during the execution of the managed runtime component; determines whether a non-deterministic event is to be logged in event logs during the execution of the managed runtime component; determines, when the non-deterministic event is to be logged, whether semantics of the non-deterministic event to be logged include a predetermined semantic, wherein the predetermined semantic includes one or more of optimistic zero copy actions; and logs, when the semantics of the non-deterministic event include the predetermined semantic, a copy of contents of the non-deterministic event in the event logs during the execution of the managed runtime component. 10. The system according to claim 9 , wherein the one or more of optimistic zero copy actions includes an immutable semantic pointer save. 11. The system according to claim 9 , wherein the one or more of optimistic zero copy actions includes a copy-on-write (“COW”) semantic pointer save. 12. The system according to claim 9 , wherein when the non-deterministic event having the semantics that include the one or more optimistic zero copy actions is on demand, values of the contents of the non-deterministic event are, on demand, copied into the event logs for storage or transmission. 13. The system according to claim 9 , wherein the managed runtime environment, when executed by the at least one processor further: records a sequence of snapshots of the managed runtime environment during the execution of the managed runtime component. 14. The system according to claim 13 , wherein the managed runtime environment, when executed by the at least one processor further: performs time travel debugging by replaying at least a portion of the execution of the managed runtime component based at least in part on a snapshot from the sequence of snapshots and at least a portion of the event logs. 15. The system according to claim 13 , wherein the managed runtime environment, when executed by the at least one processor further: performs automated failure root-cause analysis by replaying at least a portion of the execution of the managed runtime component based at least in part on a snapshot from the sequence of snapshots and at least a portion of the event logs. 16. The system according to claim 13 , wherein the managed runtime environment, when executed by the at least one processor further: performs memory use analysis by replaying at least a portion of the execution of the managed runtime component based at least in part on a snapshot from the sequence of snapshots and at least a portion of the event logs. 17. A non-transitory computer-readable medium storing instructions that, when executed by a computing system, cause the computing system to perform a method for using managed runtime environment semantics to optimize record and replay frameworks, the method including: executing, by the computing system, a managed runtime component; interacting, by the computing system, with another system during the execution of the managed runtime component; determining, by the computing system, whether a non-deterministic event is to be logged in event logs during the execution of the managed runtime component; determining, by the computing system when the non-deterministic event is to be logged, whether semantics of the non-deterministic event to be logged include a predetermined semantic, wherein the predetermined semantic includes one or more of optimistic zero copy actions; and logging, by the computing system when the semantics of the non-deterministic event include the predetermined semantic, a copy of contents of the non-deterministic event in the event logs during the execution of the managed runtime component. 18. The computer-readable medium of claim 17 , wherein the one or more of optimistic zero copy actions includes an immutable semantic pointer save. 19. The computer-readable medium of claim 17 , wherein the one or more of optimistic zero copy actions includes a copy-on-write (“COW”) semantic pointer save. 20. The computer-readable medium of claim 17 , wherein when the non-deterministic event having the semantics that include the one or more optimistic zero copy actions is on demand, values of the contents of the non-deterministic event are, on demand, copied into the event logs for storage or transmission.
Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title
of optimised code (optimisation G06F8/443) · CPC title
Workload generation, e.g. scripts, playback · CPC title
Dumping, i.e. gathering error/state information after a fault for later diagnosis · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.