Component tagging
    1.
    发明申请
    Component tagging 审中-公开
    组件标记

    公开(公告)号:US20070169045A1

    公开(公告)日:2007-07-19

    申请号:US11291864

    申请日:2005-12-01

    IPC分类号: G06F9/45

    CPC分类号: G06F11/3409

    摘要: A component tagging system for tagging various components and sub-components used by various processes allows creating a plurality of component tags for various components used in processes in a manner so that the component tags may be used in tracking various resources used by the components. The component tagging system also allows tracking usage of resources by various threads in process thread-pools, wherein the various threads may perform a service or a function on behalf of the components. An alternate embodiment of the component tagging system allows tagging of multi-process components wherein the multi-process components may be used to perform a service or a function across multiple processes.

    摘要翻译: 用于标记由各种处理使用的各种组件和子组件的组件标记系统允许以以使得组件标签可以用于跟踪由组件使用的各种资源的方式来创建用于过程中的各种组件的多个组件标签。 组件标签系统还允许通过进程线程池中的各种线程跟踪资源的使用,其中各种线程可以代表组件执行服务或功能。 组件标签系统的替代实施例允许对多进程组件进行标记,其中多进程组件可用于跨多个进程执行服务或功能。

    Minimizing user disruption during modification operations
    5.
    发明授权
    Minimizing user disruption during modification operations 有权
    在修改操作期间最大限度地减少用户中断

    公开(公告)号:US07873957B2

    公开(公告)日:2011-01-18

    申请号:US11494320

    申请日:2006-07-27

    IPC分类号: G06F9/44

    CPC分类号: G06F8/61

    摘要: A reboot reduction infrastructure may be used by applications to make installing modifications as unobtrusive as possible. Applications may register with the reboot reduction infrastructure and use provided APIs to detect which applications and services have files in use, shutdown down those applications with files in use and then restart those applications in a form similar to which they were in when the applications were shut down.

    摘要翻译: 应用程序可能会使用重新启动减少基础设施,使安装修改尽可能不引人注目。 应用程序可以注册重新启动减少基础设施,并使用提供的API来检测哪些应用程序和服务具有正在使用的文件,使用正在使用的文件关闭这些应用程序,然后以类似于应用程序关闭时的方式重新启动这些应用程序 下。

    Automatically resource leak diagnosis and detecting process within the operating system
    6.
    发明授权
    Automatically resource leak diagnosis and detecting process within the operating system 有权
    自动资源泄漏诊断和检测过程在操作系统内

    公开(公告)号:US07774741B2

    公开(公告)日:2010-08-10

    申请号:US11438791

    申请日:2006-05-22

    IPC分类号: G06F9/44 G06F9/445

    摘要: The resource leak detector attempts to identify the causes of resource leaks and fix the causes if possible. At a minimum, the located resource leaks are reported to an operating system manufacture for additional study and possible correction, either by the operating system manufacturer or the application manufacturer that is causing the resource leak. In an embodiment, in operation, a leak trigger for starting leak detection is started. If the leak trigger is activated, leak detection is started when an application begins. Resource allocations are tracked for the leaked resource and each leaked resource is matched to a corresponding allocation call stack. A type of the leaked resource may be identified. The leak detection and the leak trigger may be controlled according to at least one of a local policy and a global policy. The local and the global policy may be updated dynamically such as by using aggregated occurrences of applications that met the local policy or by matching a plurality of distinct types of leaked resources to the same call stack. A leak report may be generated of resource leak data where the leak report is stored locally or communicated to a local aggregation database or remote aggregation database. The leak report may include total leaked allocations, total size of leaked allocations, total outstanding allocations, total size of outstanding allocations and matched allocation call stacks. The leaked resource may be automatically reclaimed and a fix to the leaked resource may be created and applied automatically.

    摘要翻译: 资源泄漏检测器尝试识别资源泄漏的原因,并尽可能地修复原因。 至少,定位的资源泄漏报告给操作系统制造商,以进行额外的研究和可能的纠正,由操作系统制造商或引起资源泄漏的应用程序制造商。 在一个实施例中,在操作中,开始用于启动泄漏检测的泄漏触发。 如果泄漏触发器被激活,则在应用程序开始时开始泄漏检测。 为泄漏的资源跟踪资源分配,并且每个泄露的资源与相应的分配调用堆栈匹配。 可以识别泄漏的资源的类型。 可以根据本地策略和全局策略中的至少一个来控​​制泄漏检测和泄漏触发。 可以动态地更新本地和全局策略,例如通过使用满足本地策略的聚合发生的应用,或者通过将多个不同类型的泄露资源匹配到相同的调用堆栈来进行。 泄漏报告可能会生成泄漏报告,泄漏报告在本地存储或传送到本地聚合数据库或远程聚合数据库。 泄漏报告可能包括总泄漏分配,泄漏分配的总大小,未完成分配的总数,未完成分配的总大小以及匹配的分配调用堆栈。 泄漏的资源可以自动回收,并且可以自动创建并应用对泄漏的资源的修复。