Abstract: The present technology monitors events that allocate and deallocate virtual memory regions in a device, wherein the events include system calls from user space. The system can generate a log of events, and based on the log of events, track regions of virtual memory allocated and deallocated via the events. The system can also record events with corresponding stack traces. Next, the system can group recorded events having matching stack traces to yield event groupings, and instrument functions in a compiled code associated with the process to determine retain counts of respective events associated with the functions. The system can then automatically pair at least one of a first portion of the events and a second portion of the respective events based on the event groupings and the retain counts of the respective events to yield paired events.

Abstract: The present technology monitors events that allocate and deallocate virtual memory regions in a device, wherein the events include system calls from user space. The system can generate a log of events, and based on the log of events, track regions of virtual memory allocated and deallocated via the events. The system can also record events with corresponding stack traces. Next, the system can group recorded events having matching stack traces to yield event groupings, and instrument functions in a compiled code associated with the process to determine retain counts of respective events associated with the functions. The system can then automatically pair at least one of a first portion of the events and a second portion of the respective events based on the event groupings and the retain counts of the respective events to yield paired events.

Abstract: The present technology monitors events that allocate and deallocate virtual memory regions in a device, wherein the events include system calls from user space. The system can generate a log of events, and based on the log of events, track regions of virtual memory allocated and deallocated via the events. The system can also record events with corresponding stack traces. Next, the system can group recorded events having matching stack traces to yield event groupings, and instrument functions in a compiled code associated with the process to determine retain counts of respective events associated with the functions. The system can then automatically pair at least one of a first portion of the events and a second portion of the respective events based on the event groupings and the retain counts of the respective events to yield paired events.

Abstract: When queuing work items for asynchronous execution, the approaches set forth herein enable a debugger to provide more meaningful and complete stack trace information for enqueued work items. An example system identifies a work item to be enqueued for asynchronous execution as a separate thread during runtime of a program. Upon enqueuing the work item in an execution queue, the system captures pre-queue stack trace information associated with the work item, and associates the pre-queue stack trace information with the work item. The system removes the work item from the execution queue for execution, wherein the execution is associated with current stack trace information separate from the pre-queue stack trace information. Upon detecting an event associated with executing the work item, the system merges the pre-queue stack trace information with the current stack trace information to yield a merged stack trace.

Abstract: The subject disclosure relates to methods and systems for facilitating software development. In particular, aspects of the technology relate to a method including steps for receiving source code from a user in an editor window, automatically compiling the source code to produce compiled code, and executing the compiled code to generate an output, wherein the output comprises one or more results from execution of the compiled code. In some aspects, the method can also include steps for providing a results window to the user, the results window displaying at least one of the results from the execution of the compiled code, and providing a visualization window to the user, wherein the visualization window is associated with a progress timeline and wherein the visualization window is configured to display an animation of the at least one of the results from execution of the compiled code.

Abstract: When queuing work items for asynchronous execution, the approaches set forth herein enable a debugger to provide more meaningful and complete stack trace information for enqueued work items. An example system identifies a work item to be enqueued for asynchronous execution as a separate thread during runtime of a program. Upon enqueuing the work item in an execution queue, the system captures pre-queue stack trace information associated with the work item, and associates the pre-queue stack trace information with the work item. The system removes the work item from the execution queue for execution, wherein the execution is associated with current stack trace information separate from the pre-queue stack trace information. Upon detecting an event associated with executing the work item, the system merges the pre-queue stack trace information with the current stack trace information to yield a merged stack trace.

Abstract: The present technology monitors events that allocate and deallocate virtual memory regions in a device, wherein the events include system calls from user space. The system can generate a log of events, and based on the log of events, track regions of virtual memory allocated and deallocated via the events. The system can also record events with corresponding stack traces. Next, the system can group recorded events having matching stack traces to yield event groupings, and instrument functions in a compiled code associated with the process to determine retain counts of respective events associated with the functions. The system can then automatically pair at least one of a first portion of the events and a second portion of the respective events based on the event groupings and the retain counts of the respective events to yield paired events.

Abstract: Various technologies and techniques are disclosed that dynamically implement method selections based on declarative requirements and interaction scope. Requirements that describe when each of multiple methods that can perform a particular operation should be called can be declared using a declarative syntax. Based upon a program event, the system determines that a request should be made to select a most appropriate method of the available methods to call to perform the particular operation. Upon receiving the request to select the most appropriate method, a sort process is executed that uses an interaction scope of a current user context in combination with a plurality of sort rules to generate a sorted list of the available methods into a particular order based upon appropriateness. A most appropriate method, if any, is returned to the calling application, and then called to perform the particular operation.

Abstract: A system and method providing status information about a task being processed on a computer system is described. The task comprises an operation that blocks user activity, such as a modal task. Status information about the task is obtained during processing of the task on an event thread of a computer system. A status display is generated based upon this status information. The task yields time on the event thread, enabling the status information to be displayed in the user interface of the computer system.

Abstract: Various technologies and techniques are disclosed that dynamically implement method selections based on declarative requirements and interaction scope. Requirements that describe when each of multiple methods that can perform a particular operation should be called can be declared using a declarative syntax. Based upon a program event, the system determines that a request should be made to select a most appropriate method of the available methods to call to perform the particular operation. Upon receiving the request to select the most appropriate method, a sort process is executed that uses an interaction scope of a current user context in combination with a plurality of sort rules to generate a sorted list of the available methods into a particular order based upon appropriateness. A most appropriate method, if any, is returned to the calling application, and then called to perform the particular operation.