Method for monitoring function execution

• US 20060235655A1
• Filed: 04/18/2005
• Published: 10/19/2006
• Est. Priority Date: 04/18/2005
• Status: Abandoned Application

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: Shenfield, Michael, Doktorova, Laura, Vitanov, Kamen B., Rogers, Jeffrey Christopher, Qing, Richard X.
• Application Number:
  US11/108,059
• Publication Number:
  US 20060235655A1
• Time in Patent Office: Days
• US Class Current: 702/186
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

An endless script or other function is considered to be malicious as it exhausts system resources such as CPU time and memory. Therefore, the handling of an endless function execution is crucial, particularly in a wireless runtime environment. A combination of time-out and user-interruption scheme is used to detect and handle the problem.

Claims

1. A method for monitoring the execution of a function, said method comprising:

monitoring at least one parameter associated with an execution of a function; and

stopping the execution of the function in response to a failure to comply with at least one of said at least one parameter.

2. The method as claimed in claim 1, wherein said monitoring begins in response to an event.

3. The method as claimed in claim 1, wherein said monitoring comprises collecting usage information data according to said function to be monitored.

4. The method as claimed in claim 3, wherein said collecting of said usage information data begins after expiration of a delay.

5. The method as claimed in claim 4, wherein said delay is determined depending on said function to be monitored.

6. The method as claimed in claim 3, comprising providing an indication to a user in response to said collecting usage information data.

7. The method as claimed in claim 6, wherein said providing an indication comprises suggesting to said user to stop execution of the function in the case of a failure to comply with at least one of said at least one parameter.

8. The method as claimed in claim 7, wherein said stopping the execution is further responsive to a user input in reply to said suggesting.

9. The method as claimed in claim 3, wherein said collecting of said usage information data comprises collecting information data from at least one of a resource, a service and said function.

10. The method as claimed in claim 7, wherein said providing of an indication to a user in response to said collecting usage information data further comprises processing said collected usage information data and further wherein said indication is provided in accordance with said processing of said collected usage information data.

12. A computer readable memory comprising a plurality of instructions for configuring a processor when executed to perform the method as claimed in claim 1.

11. A method for monitoring an application comprising a plurality of function execution threads, the method comprising:

monitoring at least one parameter associated with an execution of said plurality of function execution threads;

identifying at least one of the plurality of functions threads having a corresponding parameter which does not comply; and

stopping an execution of the at least one of the plurality of function execution threads in response to said identifying.

13. A device for processing data comprising:

a processor coupled to a memory storing instructions and data to configure the processor to run at least one function execution thread, said instructions and data further configuring the processor to;

monitor at least one parameter associated with the function execution thread; and

stop executing said function execution thread in response to a failure to comply with at least one of said at least one parameter.