WO2023193632A1

WO2023193632A1 - Audio thread processing method and apparatus, computer device and storage medium

Info

Publication number: WO2023193632A1
Application number: PCT/CN2023/084321
Authority: WO
Inventors: 袁章敬; 潘风; 周暄承; 史岩峰; 曾镇城; 张冬; 孙念
Original assignee: 北京字节跳动网络技术有限公司
Priority date: 2022-04-06
Filing date: 2023-03-28
Publication date: 2023-10-12
Also published as: CN114721800A

Abstract

The present disclosure provides an audio thread processing method and apparatus, a computer device and a storage medium. The method comprises: pointing, to a preset audio processing function, a call entry of an audio instance destruction function corresponding to an application, wherein the audio instance destruction function is used for destructing a created audio instance, and the audio instance is used for audio playback; in the case of stopping audio playback, calling, by using a first thread running the audio instance, the audio processing function to which the audio instance destruction function points; acquiring a running state of an audio state notification thread detected by executing the audio processing function; and in the case that the running state indicates that the audio state notification thread feeds back audio state notification information for the audio, executing, by using the first thread, the audio instance destruction function to destruct the audio instance.

Description

Audio thread processing method, device, computer equipment and storage medium

This application claims the priority of the Chinese patent application submitted to the State Intellectual Property Office of China on April 6, 2022, with application number 202210365555.0 and the application title "An audio thread processing method, device, computer equipment and storage medium", which The entire contents are incorporated herein by reference.

Technical field

The present disclosure relates to the field of computer technology, and specifically, to an audio thread processing method, device, computer equipment and storage medium.

Background technique

When an application in the IOS system plays audio, it needs to create an audio instance for playing audio. When the audio stops playing, the thread running the audio instance will call the destruction function to destroy the audio instance. But at the same time, the IOS system also runs an audio status notification thread for notifying the status information of each audio played in the system. When the audio stops playing, the audio status notification thread also needs to be run to generate notification information for notifying the audio to stop playing and feed it back to the application.

In this way, when a certain audio stops playing, the audio status notification thread and the audio instance destruction thread will run at the same time, which will cause the system to freeze or even crash.

Contents of the invention

Embodiments of the present disclosure provide at least an audio thread processing method, device, computer equipment, and storage medium.

In a first aspect, embodiments of the present disclosure provide an audio thread processing method, including:

Point the call entry of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback;

When the audio stops playing, use the first thread running the audio instance to call the audio processing function pointed to by the audio instance destruction function;

Obtain the running status of the audio status notification thread detected by executing the audio processing function;

When the running status indicates that the audio status notification thread has fed back the audio status notification information for the audio, the first thread is used to execute the audio instance destruction function to destroy the audio instance.

In a possible implementation, the running status of the audio status notification thread is detected according to the following steps:

Determine the audio status notification thread from a plurality of threads running in the application;

Obtain the instruction address pointed by the audio status notification thread at the current moment, and determine whether the audio status notification thread is in an idle state based on the instruction address;

If so, suspend the execution of the audio status notification thread, and perform a stack traceback operation on the audio status notification thread to determine the call stack information corresponding to the audio status notification thread;

The running status is determined based on the call stack information.

In a possible implementation, the method further includes:

When it is determined that the audio status notification thread is not in an idle state, wait for the first preset time and then return to the step of obtaining the instruction address pointed by the audio status notification thread at the current moment until the audio status notification thread is determined. In idle state.

In a possible implementation, determining the running status based on the call stack information includes:

From the multiple call library addresses included in the call stack information, determine whether there is a target call library address corresponding to the target logic library; audio interruption processing logic information is stored in the target logic library, and the audio interruption processing logic Information is used to generate audio status notification information;

If the target call library address does not exist, determining the running status includes: the audio status notification thread has fed back the audio status notification information for the audio.

In a possible implementation, the method further includes:

When the target call library address exists in multiple call library addresses, resume execution of the audio status notification thread, and return to execution after waiting for the second preset time period to obtain the audio status notification thread at the current moment. The step of pointing to the instruction address is until it is determined that the target call library address does not exist among the plurality of call library addresses.

In a possible implementation, after using the first thread to execute the audio instance destruction function to destroy the audio instance, the method further includes:

Resume execution of the audio status notification thread to use the executed audio status notification thread to generate audio status notification information for other audios and feed it back to the application.

In a possible implementation, the instruction address includes a program counter PC address and a return address;

Determining whether the audio status notification thread is in an idle state according to the instruction address includes:

When it is determined that both the PC address and the return address match the address corresponding to the target function body, it is determined that the audio status notification thread is in an idle state.

In a possible implementation, before detecting the audio status notification thread's running status, it also includes:

Determine the reference information corresponding to the audio instance, and store the reference information;

Using the first thread to execute the audio instance destruction function to destroy the audio instance includes:

According to the stored reference information, the storage location of the audio instance is determined, and the first thread is used to execute the audio instance destruction function to destroy the audio instance at the storage location.

In a second aspect, embodiments of the present disclosure also provide an audio thread processing device, including:

The first processing module is used to point the call entry of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback;

A calling module, configured to use the first thread running the audio instance to call the audio processing function pointed to by the audio instance destruction function when the audio stops playing;

An acquisition module, used to acquire the running status of the audio status notification thread detected by executing the audio processing function;

Execution module, configured to use the first thread to execute the audio instance destruction function to destroy the audio instance destruction function when the running status indicates that the audio status notification thread has fed back the audio status notification information for the audio. Audio example.

In a possible implementation, the device further includes:

Detection module, used to detect the running status of the audio status notification thread according to the following steps

The running status is determined based on the call stack information.

In a possible implementation, the detection module is also configured to wait for a first preset period of time before returning to execute the acquisition of the audio when it is determined that the audio status notification thread is not in an idle state. The step of determining the instruction address pointed by the status notification thread at the current moment until it is determined that the audio status notification thread is in an idle state.

In a possible implementation, the detection module is configured to determine whether there is a target call library address corresponding to the target logical library from the multiple call library addresses included in the call stack information; Audio interruption processing logic information is stored, and the audio interruption processing logic information is used to generate audio status notification information;

In a possible implementation, the detection module is further configured to resume execution of the audio status notification thread when the target call library address exists among multiple call library addresses, and wait for the third call library address. After a preset period of time, return to the step of obtaining the instruction address pointed by the audio status notification thread at the current moment until it is determined that the target call library address does not exist among the multiple call library addresses.

In a possible implementation, the device further includes:

A second processing module configured to, after using the first thread to execute the audio instance destruction function to destroy the audio instance, resume execution of the audio status notification thread to utilize the executed audio status notification Thread, generates audio status notification information for other audios and feeds it back to the application.

The detection module is configured to determine that the audio status notification thread is in an idle state when it is determined that the PC address and the return address both match the address corresponding to the target function body.

In a possible implementation, the device further includes a storage module:

The storage module is used to determine the reference information corresponding to the audio instance and store the reference information before detecting the running status of the audio status notification thread;

The execution module is configured to determine the storage location of the audio instance according to the stored reference information, and use the first thread to execute the audio instance destruction function to destroy the audio at the storage location. Example.

In a third aspect, an optional implementation manner of the present disclosure also provides a computer device, a processor, and a memory. The memory stores machine-readable instructions executable by the processor, and the processor is configured to execute the instructions stored in the memory. machine-readable instructions. When the machine-readable instructions are executed by the processor, the When the machine-readable instructions are executed by the processor, the steps in the above-mentioned first aspect or any possible implementation manner of the first aspect are performed.

In a fourth aspect, an optional implementation manner of the present disclosure also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is run, it executes the above-mentioned first aspect, or any of the first aspects. steps in a possible implementation.

For a description of the effects of the above-mentioned audio thread processing device, computer equipment, and computer-readable storage medium, please refer to the description of the above-mentioned audio thread processing method, and will not be described again here.

The audio thread processing method, device, computer equipment and storage medium provided by the embodiments of the present disclosure use the first thread to call the audio processing function pointed to by the audio instance destruction function when the audio stops playing, and then detect the audio thread by executing the audio processing function. The running status of the audio status notification thread can accurately determine whether the audio status notification thread has fed back the audio status notification information for the audio that has stopped playing before using the first thread to execute the audio instance destruction function to destroy the audio instance. . Then, when it is determined that the audio status notification information has been fed back, the first thread is used to execute the audio instance destruction function to destroy the audio instance. In this way, using the preset audio processing function to limit the execution order of the audio status notification thread and the first thread that destroys the audio instance will not affect the operation of the first thread that destroys the audio instance and the audio status notification thread in the system, but also This avoids the concurrent execution of the audio status notification thread and the first thread that destroys the audio instance; furthermore, it avoids the problem of system lag or crash caused by two threads competing for system resources.

In order to make the above-mentioned objects, features and advantages of the present disclosure more obvious and understandable, preferred embodiments are given below and described in detail with reference to the accompanying drawings.

Description of the drawings

In order to explain the technical solutions of the embodiments of the present disclosure more clearly, the drawings required to be used in the embodiments will be briefly introduced below. The drawings here are incorporated into the specification and constitute a part of this specification. These drawings are The drawings illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure, and therefore should not be regarded as limiting the scope. For those of ordinary skill in the art, without exerting creative efforts, they can also Other relevant drawings are obtained based on these drawings.

Figure 1 shows a flow chart of an audio thread processing method provided by an embodiment of the present disclosure;

Figure 2 shows a specific implementation flow chart of an audio thread processing method provided by an embodiment of the present disclosure;

Figure 3 shows a schematic diagram of an audio thread processing device provided by an embodiment of the present disclosure;

FIG. 4 shows a schematic structural diagram of a computer device provided by an embodiment of the present disclosure.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only These are some embodiments of the present disclosure, but not all embodiments. The components of the disclosed embodiments generally described and illustrated herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the disclosure is not intended to limit the scope of the claimed disclosure, but rather to represent selected embodiments of the disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without any creative efforts shall fall within the scope of protection of the present disclosure.

In addition, the terms "first", "second", etc. in the description and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein.

The "multiple or several" mentioned in this article means two or more. "And/or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the related objects are in an "or" relationship.

Research has found that when audio in the iOS system stops playing, an audio status notification thread usually appears, competing with the thread that destroys the audio instance for system resources, causing audio applications and systems to freeze or even freeze.

Based on the above research, the present disclosure provides an audio thread processing method, device, computer equipment and storage medium, which uses a preset audio processing function to limit the execution order of the audio status notification thread and the first thread that destroys the audio instance, that is, It will not affect the operation of the first thread that destroys the audio instance and the audio status notification thread in the system. It also avoids the concurrent execution of the audio status notification thread and the first thread that destroys the audio instance. Furthermore, it avoids the two threads competing for system resources. , causing the system to freeze or crash.

The defects in the above solutions are all the results obtained by the inventor after practice and careful study. Therefore, the discovery process of the above problems and the solutions proposed by the present disclosure to the above problems below are Solutions should be the inventor's contribution to this disclosure during the process of this disclosure.

It should be noted that similar reference numerals and letters represent similar items in the following figures, therefore, once an item is defined in one figure, it does not need further definition and explanation in subsequent figures.

It should be noted that the specific nouns mentioned in the embodiments of this disclosure include:

Program Counter (PC): is a register in a computer processor that contains the address of the instruction currently being executed. As each instruction is fetched, the memory address of the program counter is incremented by one. After each instruction is fetched, the program counter points to the next instruction in the sequence.

In order to facilitate understanding of this embodiment, a method for using online course resources disclosed in this embodiment of the disclosure is first introduced in detail. The execution subject of the method of using online course resources provided by this embodiment of the disclosure generally has certain computing capabilities. Terminal equipment or other processing equipment, where the terminal equipment can be user equipment (User Equipment, UE), mobile equipment, user terminals, terminals, personal digital processing equipment (Personal Digital Assistant, PDA), handheld devices, computer equipment, etc.; in In some possible implementations, the method of using the online course resources can be implemented by the processor calling computer-readable instructions stored in the memory.

The audio thread processing method provided by the embodiment of the present disclosure will be described below by taking the execution subject as a computer device as an example.

As shown in Figure 1, a flow chart of an audio thread processing method provided by an embodiment of the present disclosure may include the following steps:

S101: Point the calling entry point of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback.

Here, the above-mentioned application can be any application running in the IOS system and capable of audio playback. The audio instance destruction function is used in the IOS system to destroy the created audio instance (audio unit). The audio unit is created during audio playback and is used for audio playback. It can be destroyed when the audio stops playing, thereby releasing system resources. Stopping audio playback may include, but is not limited to, two situations: audio content completion and ongoing playback being interrupted.

The audio processing function (My_dispose function) is a preset processing function, which corresponds to a piece of audio processing logic and is used to detect the audio status notification thread in the system to see whether the audio status notification information for the currently stopped audio has been fed back.

During specific implementation, the GOTHook method can be used to add the audio files corresponding to the applications in the IOS system. The call entry point of the frequency instance destruction function points to the preset audio processing function. Among them, GOT is a storage table for function address information, which can store various functions corresponding to the IOS system, such as execution functions, destruction functions, replacement functions, etc. GOTHOOK is a way to replace the function address stored in the GOT table with the address corresponding to other functions.

Point the calling entry point of the audio instance destruction function corresponding to the application in the IOS system to the preset audio processing function, that is, replace the entry address corresponding to the audio instance destruction function with the address corresponding to the preset audio processing function.

Optionally, if the audio instance destruction functions corresponding to each application in the IOS system are different, the calling entry points of the audio instance destruction functions corresponding to each application can be directed to the preset audio processing function. Similarly, if each application in the IOS system corresponds to an audio instance destruction function, the call entry point of the unique audio instance destruction function can be directed to the preset audio processing function.

S102: When the audio stops playing, use the first thread running the audio instance to call the audio processing function pointed to by the audio instance destruction function.

The first thread can be any thread running in the application, and specifically it can be the thread of the audio instance corresponding to the audio that is currently stopped playing.

During specific implementation, when the audio stops playing, the first thread can be used to call the audio instance destruction function. Since the entry address corresponding to the first audio instance destruction function has been replaced with the address corresponding to the preset audio processing function, therefore, in After calling the audio instance destruction function, the audio processing function pointed to by the replaced entry address will be automatically called. In this way, the first thread running the audio instance is used to call the audio processing function pointed by the call entry point of the audio instance destruction function.

It should be noted that there is no strict execution sequence between the above S101 and S102. During specific implementation, you can use GOTHook to point the call entry of the audio instance destruction function to the preset audio processing function in advance. You can also destroy the audio instance corresponding to the application that plays the audio when it is determined that there is audio that has stopped playing. The calling entry point of the function points to a preset audio processing function, which is not specifically limited in the embodiment of the present disclosure.

S103: Obtain the running status of the audio status notification thread detected by executing the audio processing function.

Here, the audio status notification thread is a default notification thread in the IOS system, that is, AVAudioSession Notify Thread, which is used to send the audio status in the IOS system to the audio corresponding application. For example, generate a notification that the audio is currently playing, generate a notification that the audio has stopped playing, Generate a notification that audio playback is abnormal. The audio status notification thread can be created when audio playback appears for the first time in the IOS system. It can always exist after creation and is used to notify the status of each audio in the IOS system.

The running status is used to indicate whether the audio status notification thread has generated and fed back audio status notification information for the audio that is currently stopped playing.

During specific implementation, after calling the audio processing function, the audio processing function can be executed, and the running status of the audio status notification thread is detected according to the detection logic indicated by the audio processing function. Furthermore, by executing the audio processing function, the running status of the detected audio status notification thread can be obtained.

In one embodiment, the running status of the audio status notification thread can be measured according to the following steps:

Step 1: Determine the audio status notification thread from the multiple threads running in the application.

Here, an application can run multiple threads, such as audio thread, system default thread, screen display thread, etc.

During specific implementation, during the execution of the audio processing function, the audio status notification thread can be determined from multiple threads running in the application.

Step 2: Obtain the instruction address pointed by the audio status notification thread at the current moment, and determine whether the audio status notification thread is in an idle state based on the instruction address.

Here, the instruction address is used to indicate the pointer address corresponding to the audio status notification thread.

During specific implementation, after determining the audio status notification thread, you can obtain the instruction address pointed by the audio status notification thread at the current moment, and determine whether the instruction address is located in the target function body (mach_msg function body), that is, determine whether the instruction address is consistent with the The address corresponding to the mach_msg function body matches. Among them, the mach_msg function is a function used to indicate whether the thread is running in the processor.

If it is determined that the instruction address is located in the mach_msg function body, it can be determined that the audio status notification thread is in an idle state; otherwise, it can be determined that the audio status notification thread is not in an idle state, that is, it is running.

In one embodiment, when it is determined that the audio status notification thread is not in an idle state, it means that the current audio status notification thread is still executing, and a timer timer can be created, and the timer will count to the first preset duration. When, return to step 2 above until it is determined that the audio status notification thread is in an idle state.

Wherein, after the timer counts to the first preset time period, the timer waits for the first preset time period. The first preset time length may be a waiting time preset by the developer. For example, the first preset time length may be 10 seconds (S), 8S and so on.

In one embodiment, the instruction address may include at least one of a PC address and a return address corresponding to the audio status notification thread. In the case where the instruction address only includes the PC address or the return address, and it is determined that this address is located in the mach_msg function body, it can be determined that the audio status notification thread is in an idle state.

When the instruction address includes both the PC address and the return address, it is necessary to determine that both the PC address and the return address match the address corresponding to the target function body, that is, it is necessary to determine that both the PC address and the return address are located in the mach_msg function. Only when the audio status notification thread is idle can the body be determined. Otherwise, it is determined that the audio status notification thread is not idle. In this way, using the PC address and the return address to check the idle state can improve the accuracy of the idle state of the determined audio state notification thread.

Step 3: If yes, pause the execution of the audio status notification thread, and perform a stack traceback operation on the audio status notification thread to determine the call stack information corresponding to the audio status notification thread.

Here, the call stack information includes the addresses of various call libraries called by the audio status notification thread during execution.

During specific implementation of this step, if it is determined that the audio status notification thread is in an idle state, the audio status notification thread in the idle state may be suspended. At the same time, a stack backtracing operation for the audio status notification thread can be performed to determine the address of each call library called by the audio status notification thread during execution, that is, the call stack information is obtained.

Step 4: Determine the running status based on the call stack information.

During specific implementation, it can be determined according to each call library address included in the call stack information whether the audio status notification thread has fed back the audio status notification information for the audio that is currently stopped playing.

In one embodiment, step 4 can be implemented according to the following steps: determine whether there is a target call library address corresponding to the target logic library from the multiple call library addresses included in the call stack information, wherein the target logic library can specifically It is libEmbeddedSystemAUs.dylib, which stores audio interruption processing logic information. The audio interruption processing logic information is used to generate audio status notification information. Among them, libEmbeddedSystemAUs.dylib is a system library created in the IOS system to store audio interruption processing logic information.

The audio status notification thread can perform audio interruption processing operations based on the audio interruption processing logic information to generate audio status notification information.

During specific implementation, when it is determined that among the multiple call library addresses included in the call stack information, there is no target call library address corresponding to the target logic library, it can be explained that the audio status notification thread has currently finished executing the audio that is currently stopped playing. Audio interrupt processing operation. In this way, it can be determined that the running status of the audio status notification thread includes: the audio status notification thread has generated audio status notification information for the audio that is currently stopped playing, and has fed back to the application corresponding to the audio.

In another embodiment, when the target call library address exists among multiple call library addresses, resume execution of the audio status notification thread, and return to execution to obtain the audio status notification thread at the current moment after waiting for the second preset time period. The steps of pointing to the instruction address until it is determined that the target call library address does not exist among the multiple call library addresses.

Here, if it is determined that the target call library address exists among the multiple call library addresses included in the call stack information, it means that the audio status notification thread has not completed the audio interruption processing operation for the audio that is currently stopped playing, and needs to continue execution. Therefore, it is necessary to resume execution of the idle audio status notification thread that was suspended when executing step three above, and create a timer. When it is determined that the timer counts to the second preset duration, return to step two and step three above. , until it is determined that the target call library address does not exist among the multiple call library addresses included in the call stack information.

Here, the reason why we need to return to step 2 above is because during the execution process of the audio status notification thread, the corresponding instruction address it points to will change in real time. Then, the result of whether the audio status notification thread is in an idle state will also follow. Variety. Therefore, by returning to step 2 above, the idle state of the audio status notification thread can be re-determined, and then the accurate running status corresponding to the audio status notification thread can be determined.

Wherein, the above-mentioned second preset time length is also the waiting time preset by the developer, which may be equal to the first preset time length, or may not be equal to the first preset time length, and is not limited here.

S104: When the running status indicates that the audio status notification thread has fed back audio status notification information for audio, use the first thread to execute the audio instance destruction function to destroy the audio instance.

Here, the audio status notification information is used to notify the application that the audio has stopped playing.

Specifically, when the running status indicates that the audio status notification thread has fed back the audio status notification information for audio to the application, according to the above step three, it can be known that the audio status notification thread at this time has been suspended. Therefore, the first thread can be used to execute the audio instance destruction function corresponding to the audio that is currently stopped playing, so as to realize the destruction of the audio instance.

In this way, based on the above embodiments, it can be known that the detection logic indicated by the audio processing function can be specifically: First, check whether the audio status notification thread is idle. If not, wait for the first preset time period and recheck whether the audio status notification thread is idle until it is determined that the audio status notification thread is idle. If so, detect whether the target call library address corresponding to the target logic library exists among the multiple call library addresses corresponding to the audio status notification thread. If it does not exist, determine that the running status is that audio status notification information for the currently stopped playing audio has been generated. and give feedback. If it exists, wait for the second preset time period, return to execution and detect whether the audio status notification thread is idle, until it is determined that the target call library address is not included in the multiple call library addresses. Furthermore, the audio instance destruction function can be executed to destroy the audio instance.

In one embodiment, after the first thread is used to execute the audio instance destruction function to destroy the audio instance, the audio status notification thread at this time is still in a suspended state. Therefore, the execution of the audio status notification thread can also be resumed to use the executed audio status notification thread to generate audio status notification information for other audios and feed it back to the application.

In this way, by resuming the execution of the audio status notification thread, the audio status notification thread can be used to generate audio status notification information for subsequent audio played in the system, for example, generate a notification to start playing the audio currently, and generate a notification to stop the audio playing. Therefore, the audio status notification information corresponding to each audio played in the system can be obtained in time.

In one embodiment, before detecting the running status of the audio status notification thread, reference information corresponding to the audio instance may also be determined and the reference information may be stored. Among them, the reference information is used to indicate the storage location of the audio instance. For example, the reference information may be the pointer address, reference relationship, storage address and other information corresponding to the audio instance. In this way, by storing the reference information corresponding to the audio instance, the audio instance can be temporarily stored, so that the audio instance can be found later when the destruction operation is performed.

Further, when performing the step of using the first thread to execute the audio instance destruction function to destroy the audio instance, the storage location of the audio instance can be determined according to the reference information corresponding to the stored audio instance. Afterwards, the first thread can be used to execute the audio instance destruction function to destroy the audio instance stored at the storage location.

In this way, based on the above embodiments, the preset audio processing function is used to limit the execution order of the audio status notification thread and the first thread that destroys the audio instance, which will not affect the first thread that destroys the audio instance and the audio status in the system. The running of the notification thread also avoids the concurrent execution of the audio status notification thread and the first thread that destroys the audio instance; furthermore, it effectively avoids the problem of system lag or crash caused by two threads competing for system resources.

As shown in Figure 2, the specific implementation flow of an audio thread processing method provided by an embodiment of the present disclosure is A process diagram can include the following steps:

S201: Point the calling entry point of the audio instance destruction function corresponding to the application to the preset audio processing function.

S202: When the audio stops playing, use the first thread to call the audio processing function pointed to by the audio instance destruction function.

S203: Determine the audio status notification thread from multiple threads running in the application.

S204: Obtain the instruction address pointed by the audio status notification thread at the current moment, and determine whether the audio status notification thread is in an idle state based on the instruction address.

Here, the instruction address may include a PC address and a return address.

If yes, execute S205; if not, start a timer, and after the timer count reaches the first preset duration, return to execute S204 until it is determined that the audio status notification thread is in an idle state.

S205: Perform a stack traceback operation on the audio status notification thread to determine the call stack information corresponding to the audio status notification thread.

S206: Determine whether there is a target call library address corresponding to the target logical library from the multiple call library addresses included in the call stack information.

If not, determine that the running status corresponding to the audio status notification thread includes: the audio status notification thread has fed back audio status notification information for audio, and execute S207; if yes, resume execution of the audio status notification thread, and start the timer. After the timer count reaches the second preset duration, execution returns to S204 until it is determined that the target call library address does not exist among the multiple call library addresses.

S207: Use the first thread to execute the audio instance destruction function to destroy the audio instance.

S208: Resume execution of the audio status notification thread.

For the specific implementation steps of S201 to S208, reference may be made to the above embodiments and will not be described again here.

Those skilled in the art can understand that in the above-mentioned methods of specific embodiments, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be based on its function and possible The internal logic is determined.

Based on the same inventive concept, the embodiment of the present disclosure also provides an audio thread processing device corresponding to the audio thread processing method. Since the principle of solving the problem of the device in the embodiment of the present disclosure is similar to the above-mentioned audio thread processing method of the embodiment of the present disclosure, therefore For the implementation of the device, please refer to the implementation of the method, and repeated details will not be repeated.

As shown in Figure 3, a schematic diagram of an audio thread processing device provided by an embodiment of the present disclosure includes:

The first processing module 301 is used to point the call entry of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback ;

The calling module 302 is configured to use the first thread running the audio instance to call the audio processing function pointed to by the audio instance destruction function when the audio stops playing;

The acquisition module 303 is used to obtain the running status of the audio status notification thread detected by executing the audio processing function;

Execution module 304, configured to use the first thread to execute the audio instance destruction function to destroy all audio instances when the running status indicates that the audio status notification thread has fed back the audio status notification information for the audio. Describe audio examples.

In a possible implementation, the device further includes:

Detection module 305, used to detect the running status of the audio status notification thread according to the following steps

The running status is determined based on the call stack information.

In a possible implementation, the detection module 305 is also configured to wait for a first preset period of time before returning to execute the acquisition of the audio status notification thread when it is determined that the audio status notification thread is not in an idle state. The instruction address pointed to at the current moment steps until the audio status notification thread is determined to be in an idle state.

In a possible implementation, the detection module 305 is configured to determine whether there is a target call library address corresponding to the target logic library from the multiple call library addresses included in the call stack information; the target logic library Audio interruption processing logic information is stored in, and the audio interruption processing logic information is used to generate audio status notification information;

In a possible implementation, the detection module 305 is also configured to resume execution of the audio status notification thread when the target call library address exists among multiple call library addresses, and wait for After the second preset period of time, the step of obtaining the instruction address pointed by the audio status notification thread at the current moment is returned to execution until it is determined that the target call library address does not exist among the plurality of call library addresses.

In a possible implementation, the device further includes:

The second processing module 306 is configured to, after using the first thread to execute the audio instance destruction function to destroy the audio instance, resume execution of the audio status notification thread to utilize the executed audio status The notification thread generates audio status notification information for other audios and feeds it back to the application.

The detection module 305 is configured to determine that the audio status notification thread is in an idle state when it is determined that both the PC address and the return address match the address corresponding to the target function body.

In a possible implementation, the device further includes a storage module 307:

The storage module 307 is configured to determine the reference information corresponding to the audio instance and store the reference information before detecting the running status of the audio status notification thread;

The execution module 304 is configured to determine the storage location of the audio instance according to the stored reference information, and use the first thread to execute the audio instance destruction function to destroy the audio instance at the storage location. Audio example.

For a description of the processing flow of each module in the device and the interaction flow between the modules, please refer to the relevant descriptions in the above method embodiments, and will not be described in detail here.

Based on the same technical concept, embodiments of the present application also provide a computer device. Referring to Figure 4, a schematic structural diagram of a computer device provided by an embodiment of the present application includes:

Processor 41, memory 42 and bus 43. The memory 42 stores machine-readable instructions executable by the processor 41 , and the processor 41 is used to execute the machine-readable instructions stored in the memory 42 . When the machine-readable instructions are executed by the processor 41 , the processor 41 executes The following steps: S101: Point the call entry of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback; S102: when the audio stops In the case of playback, use the first thread running the audio instance to call the audio instance destruction function pointed to Audio processing function; S103: Obtain the running status of the audio status notification thread detected by executing the audio processing function and S104: In the case where the running status indicates that the audio status notification thread has fed back audio status notification information for audio, use The first thread executes the audio instance destruction function to destroy the audio instance.

The above-mentioned memory 42 includes a memory 421 and an external memory 422; the memory 421 here is also called an internal memory, and is used to temporarily store the operation data in the processor 41, as well as the data exchanged with external memory 422 such as a hard disk. The processor 41 communicates with the processor 42 through the memory 421. The external memory 422 performs data exchange. When the computer device is running, the processor 41 and the memory 42 communicate through the bus 43, so that the processor 41 executes the execution instructions mentioned in the above method embodiment.

Embodiments of the present disclosure also provide a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is run by a processor, the steps of the audio thread processing method described in the above method embodiment are executed. Wherein, the storage medium may be a volatile or non-volatile computer-readable storage medium.

The computer program product of the audio thread processing method provided by the embodiment of the present disclosure includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the audio thread processing method described in the above method embodiment. For details of the steps, please refer to the above method embodiments and will not be described again here.

The computer program product can be implemented specifically through hardware, software or a combination thereof. In an optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a Software Development Kit (SDK), etc. wait.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiment, and will not be described again here. In the several embodiments provided in this disclosure, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined. Or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some communication interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separate, as The components shown in a unit may or may not be a physical unit, that is, they may be located in one place, or they may be distributed over multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present disclosure. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

If the technical solution of this application involves personal information, the products applying the technical solution of this application will clearly inform the personal information processing rules and obtain the individual's independent consent before processing personal information. If the technical solution in this application involves sensitive personal information, the product applying the technical solution in this application must obtain the individual's separate consent before processing sensitive personal information, and meet the requirement of "express consent" at the same time. For example, setting up clear and conspicuous signs on personal information collection devices such as cameras to inform them that they have entered the scope of personal information collection, and that personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed to have agreed to the collection of his or her personal information; or On personal information processing devices, when using obvious logos/information to inform personal information processing rules, obtain personal authorization through pop-up messages or asking individuals to upload their personal information; among them, personal information processing rules may include personal information processing rules. Information processors, purposes of personal information processing, processing methods, types of personal information processed, etc.

Finally, it should be noted that the above-mentioned embodiments are only specific implementations of the present disclosure and are used to illustrate the technical solutions of the present disclosure rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although refer to the foregoing The embodiments describe the present disclosure in detail. Those of ordinary skill in the art should understand that any person familiar with the technical field can still modify the technical solutions recorded in the foregoing embodiments within the technical scope disclosed in the present disclosure. changes may be easily imagined, or some of the technologies Features are equivalently substituted; and these modifications, changes or substitutions do not deviate from the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and shall be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be determined by the protection scope of the claims.

Claims

An audio thread processing method, characterized by including:

Point the call entry of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback;

When the audio stops playing, use the first thread running the audio instance to call the audio processing function pointed to by the audio instance destruction function;

Obtain the running status of the audio status notification thread detected by executing the audio processing function;

When the running status indicates that the audio status notification thread has fed back the audio status notification information for the audio, the first thread is used to execute the audio instance destruction function to destroy the audio instance.
The method according to claim 1, characterized in that the running status of the audio status notification thread is detected according to the following steps:

Determine the audio status notification thread from a plurality of threads running in the application;

Obtain the instruction address pointed by the audio status notification thread at the current moment, and determine whether the audio status notification thread is in an idle state based on the instruction address;

If so, suspend the execution of the audio status notification thread, and perform a stack traceback operation on the audio status notification thread to determine the call stack information corresponding to the audio status notification thread;

The running status is determined based on the call stack information.
The method of claim 2, further comprising:

When it is determined that the audio status notification thread is not in an idle state, wait for the first preset time and then return to the step of obtaining the instruction address pointed by the audio status notification thread at the current moment until the audio status notification thread is determined. In idle state.
The method according to claim 2, wherein determining the running status according to the call stack information includes:

From the multiple call library addresses included in the call stack information, determine whether there is a target call library address corresponding to the target logic library; audio interruption processing logic information is stored in the target logic library, and the audio interruption processing logic Information is used to generate audio status notification information;

If the target call library address does not exist, determining the running status includes: the audio status notification thread has fed back the audio status notification information for the audio.
The method of claim 4, further comprising:

When the target call library address exists in multiple call library addresses, resume execution of the audio status notification thread, and return to execution after waiting for the second preset time period to obtain the audio status notification thread at the current moment. The step of pointing to the instruction address is until it is determined that the target call library address does not exist among the plurality of call library addresses.
The method according to claim 5, characterized in that, after using the first thread to execute the audio instance destruction function to destroy the audio instance, it further includes:

Resume execution of the audio status notification thread to use the executed audio status notification thread to generate audio status notification information for other audios and feed it back to the application.
The method of claim 2, wherein the instruction address includes a program counter PC address and a return address;

Determining whether the audio status notification thread is in an idle state according to the instruction address includes:

When it is determined that both the PC address and the return address match the address corresponding to the target function body, it is determined that the audio status notification thread is in an idle state.
The method according to claim 1, characterized in that before detecting the running status of the audio status notification thread, it further includes:

Determine the reference information corresponding to the audio instance, and store the reference information;

Using the first thread to execute the audio instance destruction function to destroy the audio instance includes:

According to the stored reference information, the storage location of the audio instance is determined, and the first thread is used to execute the audio instance destruction function to destroy the audio instance at the storage location.
An audio thread processing device, characterized by including:

The first processing module is used to point the call entry of the audio instance destruction function corresponding to the application to the preset audio processing function; the audio instance destruction function is used to destroy the created audio instance; the audio instance is used for audio playback;

A calling module, configured to use the first thread running the audio instance to call the audio processing function pointed to by the audio instance destruction function when the audio stops playing;

An acquisition module, used to acquire the running status of the audio status notification thread detected by executing the audio processing function;

Execution module, configured to use the first thread to execute the audio instance destruction function to destroy the audio instance destruction function when the running status indicates that the audio status notification thread has fed back the audio status notification information for the audio. Audio example.
A computer device, characterized in that it includes: a processor and a memory, the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory, When the machine-readable instructions are executed by the processor, the processor executes the steps of the audio thread processing method according to any one of claims 1 to 8.
A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is run by a computer device, the computer device executes the method according to any one of claims 1 to 8. The steps of the audio thread processing method described above.
A computer program product, characterized in that, when the computer program product is run on a computer, it causes the computer to execute the method according to any one of claims 1-8.