Patent classifications
G06F11/0715
Hang condition mitigation for browser applications
Methods, systems, and computer program products are provided for detecting a browser hang condition and causing the browser to enter into a mitigation state. For instance, a window or tab of the browser executes via a first thread of the browser, and third-party code executes via a second thread of the browser. The first thread issues a hang resistance message to the second thread and waits for a response from the second thread. The second thread processes the hang resistance message after processing all other messages in its queue. Thus, if the first thread receives the response, the first thread determines that the second thread has not entered into a hang condition. However, if the first thread does not receive the response, the first thread determines that the second thread has entered into a hang condition and subsequently causes the browser to enter the mitigation state.
DETERMINISTIC SOFTWARE CODE DECOMPILER SYSTEM
Embodiments of the present invention provide a system for decompiling one or more codes. The system is configured for extracting a binary code and one or more inputs associated with the binary code, disassembling the binary code into a first assembly language code based on the one or more inputs, converting the first assembly language code into first set of fixed dimension vectors, generating a skeleton code from the first set of fixed dimension vectors, optimizing the skeleton code, and generating a high level code.
Runtime Performance Introspection
Operations include diagnosing performance hotspots with minimal performance impact. A system selectively extracts a subset of in-memory application data, for failure analysis, based on application metadata associated with an application. The selective data extraction may be used to generate succinct reports that are customized to explore the specific vulnerabilities of each particular application. Application metadata identifies application data attributes for value extraction. The application metadata may identify, for example, a client attribute which indicates the client which requested the execution of a failed operation (or execution of an operation with a failed sub-function). The application metadata may identify a particular function, associated with an operation, that is to be analyzed in case of operation failure. The application metadata may identify a thread-local variable of a thread, executing an operation, that is to be analyzed in case of operation failure.
System for technology anomaly detection, triage and response using solution data modeling
Embodiments of the present invention provide a system for technology anomaly detection, triage, and response using solution data modeling. The system is configured for generating solution data models comprising a plurality of asset systems and a plurality of users, continuously monitoring the plurality of asset systems and detecting an anomaly associated with the one or more tasks associated with at least a first group of asset systems of the plurality of asset systems, extracting a first solution data model associated with the first group of asset systems, identifying one or more relationships associated with the first group of systems based on the extracted first solution data model, and identifying a point of failure associated with the anomaly and the first group of asset systems based on the one or more relationships.
APPLICATION CRASH ANALYSIS TECHNIQUES WHEN MEMORY DUMP AND DEBUG SYMBOLS ARE NOT CO-LOCATED
Distributed architectures that can generate a crash report without concurrent access to debug symbols and a memory dump. Besides grabbing generic information from a memory dump, which most debuggers provide (e.g., call stack traces for all threads), developer-provided scripts can grab application-specific details such as tables of open protocol client connections and so-forth. This extraction can take place at a customer site where a crash occurred and can proceed without the use of debug symbols. The extraction can generate a crash report which can be sent back from the field. Once in the hands of engineering (e.g., at a provider site where debug symbols are extant but the memory dump is not), debug symbols can then be used in an annotation phase to fill in missing details (e.g., the precise source files and line numbers corresponding to call stack traces) without access to the original crash dump.
Vehicle and Control Method Thereof
A vehicle includes a memory configured to store predetermined points in time at which each of a plurality of tasks is to be performed, the plurality of tasks including a first task and a second task, and a detector configured to determine a malfunction of at least one processor of a plurality of processors performing the plurality of tasks, wherein the detector is configured to control the at least one processor to output trigger signals for the first task and the second task based on whether one of the first and second tasks is completed at its respective predetermined point in time.
Automated Crash Recovery
Methods for improving operation of a user device running an application. The methods include collecting a first set of data corresponding to a run time environment of the application, collecting a second set of data corresponding to a crash of the application, identifying a cause of the crash based on the first set of data and a second set of data and determining the cause of the crash is associated with an application feature corresponding to a feature flag.
Self-learning robotic process automation
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for a self-learning robotic process automation are disclosed. In one aspect, a method includes receiving an automated script that includes one or more commands and that is configured to interact with graphical elements that appear on a user interface. The method further includes executing a command of the one or more commands of the automated script. The method further includes determining that an error occurred during execution of the command of the one or more commands of the automated script. The method further includes determining a modification for the command by applying a script repair model. The method further includes executing the modified command. The method further includes determining whether the error or another error occurred during execution of the modified command. The method further includes determining whether to update the automated script with the modified command.
Application logging mechanism
A system to facilitate application logging is described. The system includes a processor and a machine readable medium storing instructions that, when executed, cause the processor to record a system state, perform application logging at a first logging rate, record an occurrence of task failures during the logging, determine a predicted queue size threshold value based on the recorded occurrence of task failures, determine whether that the predicted queue size threshold value is less than an actual queue size and perform the application logging at a second logging rate upon a determination that the predicted queue size threshold value is less than an actual queue size, wherein the second logging rate is greater than the first logging rate.
METHOD FOR GRACEFULLY HANDLING QAT HARDWARE OR CPU SOFTWARE FAILURES BY DYNAMICALLY SWITCHING BETWEEN QAT HARDWARE AND CPU SOFTWARE FOR DATA COMPRESSION AND DECOMPRESSION
A method, apparatus, and system for handling a failure of a hardware cryptography/compression accelerator is disclosed. The operations comprise: detecting that a hardware cryptography/compression accelerator at a first data storage system has failed; determining one or more failed cryptography and/or compression operation tasks that were submitted to the hardware cryptography/compression accelerator but were not completed due to the failure of the hardware cryptography/compression accelerator; and performing a remedial operation in response to the hardware cryptography/compression accelerator failure to prevent a systemic failure.