Memory Management With Bitness-Based Termination for Leak Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Memory leaks in electronic devices result in inefficient memory resource utilization due to improperly released memory, leading to system slowdowns and crashes, with existing solutions failing to consider user experience in application management.

Innovation Solution

A memory management method that checks and kills applications based on multi-dimensional information, including process bitness and duration in background state, to prevent memory leaks and optimize resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are killed based on virtual memory occupancy to resolve memory leaks, then memory resource management is improved, but user experience deteriorates due to unnecessary interference with application usage

Engineering Contradiction:
Improvememory resource managementVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent changes the parameter basis for application management from simple virtual memory occupancy to a composite parameter including bitness and duration in background state. This allows the system to distinguish between applications that genuinely need termination (32-bit apps with memory leaks) and those that should be preserved (64-bit apps or foreground apps), thereby resolving memory issues without degrading user experience.

Inventive Principle:
Principle #35Parameter changes

2Quantity of substance

If 32-bit applications are terminated to free memory, then memory availability is improved, but system compatibility worsens

Engineering Contradiction:
Improvememory availabilityVSAvoidsystem compatibility
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by treating different application types differently based on their bitness and state. Instead of a uniform termination policy, the system selectively terminates only 32-bit applications in background state with memory leaks, while preserving 64-bit applications and foreground applications. This localized approach frees memory where needed without compromising overall system compatibility.

Inventive Principle:
Principle #3Local quality

3Measurement precision

If memory threshold is set low to detect memory leaks early, then detection precision is improved, but false positive rate increases

Engineering Contradiction:
Improvememory leak detection precisionVSAvoidfalse positive rate
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent transitions from a single-dimension detection approach (virtual memory occupancy threshold) to a multi-dimensional approach by incorporating bitness and duration in background state as additional dimensions. This dimensional expansion allows the system to maintain high detection precision for memory leaks while reducing false positives, as applications are only terminated when all three criteria are met simultaneously.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP4145286B1Memory management method and electronic device
Publication Date: 2025.08.13 HONOR DEVICE CO LTD
  • EP4145286B1 patent drawingFigure 1
  • EP4145286B1 patent drawingFigure 2
  • EP4145286B1 patent drawingFigure 3

AI summary

A memory management method and an electronic device are disclosed. The method includes: starting an application and providing virtual memory to the application (S401); checking a space of the virtual memory occupied while the application is running (S402); checking bitness of a process run by the application when the space of the virtual memory occupied is greater than a first threshold (S403); and performing a process-killing operation on the application based on the bitness of the process run by the application (S404). In the foregoing method, a specific application is checked and killed according to a preset policy by combining multi-dimensional information according to occupancy of virtual memory when a memory exception occurs in a running application, so as to resolve a memory leak problem.