llfbandit / record

Audio recorder from microphone to a given file path. No external dependencies, MediaRecorder is used for Android an AVAudioRecorder for iOS.
https://pub.dev/packages/record
241 stars 204 forks source link

How to disable Logs BufferPoolAccessor #346

Closed dkliss closed 4 months ago

dkliss commented 5 months ago

Package: record: ^5.1.1

Android Emulator.

Details:

I have recently tested this package. I have one issue. Even after disposing recorder, I am getting below logs specifically on Android emulator ONLY (VS code). How to disable these when using this package on android?

D/BufferPoolAccessor2.0(29794): bufferpool2 0xec37eb28 : 7(14336 size) total buffers - 4(8192 size) used buffers - 30722/30755 (recycle/alloc) - 101/61501 (fetch/transfer) D/BufferPoolAccessor2.0(29794): bufferpool2 0xcddb8b88 : 7(14336 size) total buffers - 4(8192 size) used buffers - 31317/31355 (recycle/alloc) - 118/62701 (fetch/transfer) D/BufferPoolAccessor2.0(29794): bufferpool2 0xec37eb28 : 7(14336 size) total buffers - 4(8192 size) used buffers - 30992/31025 (recycle/alloc) - 101/62041 (fetch/transfer) D/BufferPoolAccessor2.0(29794): bufferpool2 0xcddb8b88 : 7(14336 size) total buffers - 4(8192 size) used buffers - 31587/31625 (recycle/alloc) - 118/63241 (fetch/transfer) D/BufferPoolAccessor2.0(29794): bufferpool2 0xec37eb28 : 7(14336 size) total buffers - 4(8192 size) used buffers - 31262/31295 (recycle/alloc) - 102/62581 (fetch/transfer)

A clear and concise description of what the bug is.

Add your record configuration RecordConfig(...)

const encoder = AudioEncoder.aacLc; const config = RecordConfig(encoder: encoder, numChannels: 1);

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Additional context

Add any other context about the problem here.

llfbandit commented 5 months ago

Thanks for the report.

Why are you sure this log is from the recorder? What are you doing after stopping the recorder? Do you give the audio file to an audio player or this is the end of your process?

dkliss commented 5 months ago

Thanks for the report.

Why are you sure this log is from the recorder? What are you doing after stopping the recorder? Do you give the audio file to an audio player or this is the end of your process?

This report is part of recorder logs and if i do not use recorder i do not get this in Android emulator. Currently, I do not use audio player and only recorder. Basically, i print the path file after recorder is stopped. I dont see this issue in iOS, MAC an Web but only in Android emulator.


D/MPEG4Writer( 6372): WriterThread stopped. Status:0
I/MPEG4Writer( 6372): Adjust the moov start time from 0 us -> 0 us
I/MPEG4Writer( 6372): MOOV atom was written to the file
D/MPEG4Writer( 6372): release()
D/MPEG4Writer( 6372): ftruncate mPreAllocateFileEndOffset:180029 mOffset:2585 mMdatEndOffset:176733 diff:3296
D/MPEG4Writer( 6372): MP4WtrCtrlHlpLooper stopped
D/MPEG4Writer( 6372): Top 5 write durations(microseconds): #1:425 #2:430 #3:473 #4:540 #5:927
D/MPEG4Writer( 6372): reset()
D/MPEG4Writer( 6372): Audio track stopping. Stop source
E/MPEG4Writer( 6372): Stop() called but track is not started or stopped
I/flutter ( 6372):  Observer: info: Closing: Recorder
D/BufferPoolAccessor2.0( 6372): bufferpool2 0xb038c7e8 : 0(0 size) total buffers - 0(0 size) used buffers - 532/539 (recycle/alloc) - 4/1068 (fetch/transfer)
D/BufferPoolAccessor2.0( 6372): bufferpool2 0xb038e168 : 0(0 size) total buffers - 0(0 size) used buffers - 22/29 (recycle/alloc) - 4/48 (fetch/transfer)
D/BufferPoolAccessor2.0( 6372): evictor expired: 1, evicted: 1
D/BufferPoolAccessor2.0( 6372): evictor expired: 1, evicted: 0
D/BufferPoolAccessor2.0( 6372): bufferpool2 0xb03b3468 : 0(0 size) total buffers - 0(0 size) used buffers - 5/11 (recycle/alloc) - 3/12 (fetch/transfer)
D/BufferPoolAccessor2.0( 6372): evictor expired: 1, evicted: 1
llfbandit commented 4 months ago

I tried to figure out what was going on but it seems there's nothing wrong in package source code. Unless, you catch something for further investigation I won't spend more time on this because apps are not run on emulators in real life.