Monitoring application loading

• US 9,513,961 B1
• Filed: 04/02/2014
• Issued: 12/06/2016
• Est. Priority Date: 04/02/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Guajardo-Cespedes, Mario, Hendriks, Erik, Knych, Thomas William, Wang, Chen
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Rivera, Anibal
• Application Number:
  US14/243,030
• Time in Patent Office: 979 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3644 by instrumenting at runtime
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45516 Runtime code conversion or optimisation
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for determining when an application is sufficiently instantiated to be subject to a crawling operation. In one aspect, a method includes instantiating an instance of a native application that generates environment instances for display on a user device within the native application instance; monitoring requests for content sent from the native application instance to serving entities that are external to the native application instance; determining whether each monitored request has been fulfilled; in response to determining that the requests are fulfilled: determining whether each thread in a set of threads of the native application instance is idle, generating a load signal in response to determining each thread in the set of thread of the native application instance is idle, the load signal indicating the native application instance is sufficiently instantiated to be subject to a crawling operation.

Claims

1. A computer-implemented method performed by data processing apparatus, the method comprising:

instantiating, in a computer, an instance of a native application that generates environment instances for display on a user device within the native application instance;

monitoring, at the computer, requests for content sent from the native application instance executing in the computer to serving entities that are external to the native application instance and the computer;

determining whether each monitored request of the requests has been fulfilled indicating no monitored request is unfulfilled;

in response to determining that each monitored request of the requests has been fulfilled;

determining whether each thread in a set of threads of the native application instance is idle, wherein the determination of whether each thread in the set of threads of the native application instance is idle is done after the determination that each monitored request in the set of requests have been fulfilled;

generating a load signal in response to determining that each thread in the set of threads of the native application instance is idle, the load signal indicating the native application instance is finished loading sufficiently instantiated to be subject to a crawling operation; and

in response to the load signal, crawling content of the native application instance.

2. The computer-implemented method of claim 1, wherein determining whether each thread in the set of threads of the native application instance is idle comprises:

initiating a timer in response to determining that each monitored request has been fulfilled, the timer expiring after a timer period; and

determining whether each thread in the set of threads of the native application instance is idle only after the time expires after the timer period.

3. The computer-implemented method of claim 2, wherein determining whether each monitored request has been fulfilled comprises determining, for each monitored request, that content requested by each request has been received by the instance of the native application in response to the request.

4. The computer-implemented method of claim 3, wherein determining whether each thread in the set of threads of the native application instance is idle comprises:

monitoring inter-process communication (IPC) calls of the threads; and

determining the set of threads of the native application instance are not idle when at least one IPC call is not fulfilled.

5. The computer-implemented method of claim 4, wherein determining whether each thread in the set of threads of the native application instance is idle further comprises determining whether each thread in a set of user interface (UI) worker threads is idle.

6. The computer-implemented method of claim 5, wherein determining whether each thread in the set of threads of the native application instance is idle further comprises:

determining whether a message queue for the UI worker threads is empty; and

determining whether each thread in the UI worker threads is idle in response to determining the message queue for the UI worker threads is idle.

7. The computer-implemented method of claim 1, wherein determining whether each monitored request has been fulfilled comprises determining, for each monitored request, that content requested by each request has been received by the instance of the native application in response to the request.

8. The computer-implemented method of claim 1, wherein determining whether each monitored request has been fulfilled comprises determining, for each monitored request, that content requested by each request has been received by the instance of the native application in response to the request or that the request has timed out.

9. The computer-implemented method of claim 1, wherein determining whether each thread in the set of threads of the native application instance is idle comprises:

monitoring inter-process communication (IPC) calls of the threads; and

determining the set of threads of the native application instance are not idle when at least one IPC call is not fulfilled.

10. The computer-implemented method of claim 1, determining whether each thread in the set of threads of the native application instance is idle comprises determining whether each thread in a set of user interface (UI) worker threads is idle.

11. The computer-implemented method of claim 10, wherein determining whether each thread in the set of threads of the native application instance is idle further comprises:

determining whether a message queue for the UI worker threads is empty; and

determining whether each thread in the UI worker threads is idle in response to determining the message queue for the UI worker threads is idle.

12. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by data processing apparatus cause the data processing apparatus to perform operations comprising:

instantiating, in a computer, an instance of a native application that generates environment instances for display on a user device within the native application instance;

monitoring, at the computer, requests for content sent from the native application instance executing in the computer to serving entities that are external to the native application instance and the computer;

determining whether each monitored request of the requests has been fulfilled indicating no monitored request is unfulfilled;

in response to determining that each monitored request of the requests has been fulfilled;

determining whether each thread in a set of threads of the native application instance is idle, wherein the determination of whether each thread in the set of threads of the native application instance is idle is done after the determination that each monitored request in the set of requests has been fulfilled;

generating a load signal in response to determining that each thread in the set of threads of the native application instance is idle, the load signal indicating the native application instance is finished loading to be subject to a crawling operation; and

in response to the load signal, crawling content of the native application instance.

13. A system, comprising:

a data processing apparatus; and

software stored in non-transitory computer readable storage medium storing instructions executable by the data processing apparatus and that upon such execution cause the data processing apparatus to perform operations comprising;

instantiating, in a computer, an instance of a native application that generates environment instances for display on a user device within the native application instance;

monitoring, at the computer, requests for content sent from the native application instance executing in the computer to serving entities that are external to the native application instance and the computer;

determining whether each monitored request of the requests has been fulfilled indicating no monitored request is unfulfilled;

in response to determining that each monitored request of the requests has been fulfilled;

determining whether each thread in a set of threads of the native application instance is idle, wherein the determination of whether each thread in the set of threads of the native application instance is idle is done after the determination that each monitored request in the set of requests has been fulfilled;

generating a load signal in response to determining that each thread in the set of threads of the native application instance is idle, the load signal indicating the native application instance is finished loading to be subject to a crawling operation; and

in response to the load signal, crawling content of the native application instance.

14. The system of claim 13, wherein determining whether each thread in the set of threads of the native application instance is idle comprises:

initiating a timer in response to determining that the each monitored request has been fulfilled, the timer expiring after a timer period; and

determining whether each thread in the set of threads of the native application instance is idle only after the time expires after the timer period.

15. The system of claim 14, wherein determining whether each monitored request has been fulfilled comprises determining, for each monitored request, that content requested by each request has been received by the instance of the native application in response to the request.

16. The system of claim 15, wherein determining whether each thread in the set of threads of the native application instance is idle comprises:

monitoring inter-process communication (IPC) calls of the threads; and

determining the set of threads of the native application instance are not idle when at least one IPC call is not fulfilled.

17. The system of claim 16, wherein determining whether each thread in the set of threads of the native application instance is idle further comprises determining whether each thread in a set of user interface (UI) worker threads is idle.

18. The system of claim 17, wherein determining whether each thread in the set of threads of the native application instance is idle further comprises:

determining whether a message queue for the UI worker threads is empty; and

determining whether each thread in the UI worker threads is idle in response to determining the message queue for the UI worker threads is idle.

19. The system of claim 13, wherein determining whether each monitored request has been fulfilled comprises determining, for each monitored request, that content requested by each request has been received by the instance of the native application in response to the request or that the request has timed out.

20. The system of claim 13, wherein determining whether each thread in the set of threads of the native application instance is idle comprises:

monitoring inter-process communication (IPC) calls of the threads; and

determining the set of threads of the native application instance are not idle when at least one IPC call is not fulfilled.

21. The system of claim 13, wherein determining whether each thread in the set of threads of the native application instance is idle comprises determining whether each thread in a set of user interface (UI) worker threads is idle.