iOS Camera resolution crash

[SubashManian]

Bar Code scanner won't run iPhone 8 device while set it max resolution. if i set resolution to medium at the time it work's fine but can't able to scan the lower quality bar code in printed copies.

While i set it to max resolution for android it takes the resolution automatically based on the device configuration. but it's not work on iOS

CameraMlVision<List>(
resolution: ResolutionPreset.max,
overlayBuilder: (c) {
return Container(
decoration: ShapeDecoration(
shape: _ScannerOverlayShape(
borderColor: Theme.of(context).primaryColor,
borderWidth: 3.0,
),
),
);
},
detector: FirebaseVision.instance.barcodeDetector().detectInImage,
onResult: (List barcodes) {
},
onDispose: () {
detector.close();
},

[Kleak]

You should open an issue on the camera plugin since we use it under the hood.

[SubashManian]

But while set to max resolution iphone 8 memory consumption is more than gb and it leads to crash

[Kleak]

The only thing we do in this package is getting the video stream from camera plugin and plug it into flutter_firebase_ml_vision plugin.
and we can't fix problem in those package so you will have to open issue on their repository.

[SubashManian]

Hi @Kleak
I have updated both the flutter and camera plugin to the latest version and tested with high & max resolution with their official sample project, it works fine.
Also i have checked the memory usage it doesn't exceeds 500MB, but when i test the official example of flutter_camera_ml_vision with high & max resolution, it crashes.
please advice

I have attached the image of camera result in max resolution

[vasilich6107]

@SubashManian the memory leak crash is known feature of this package. The same works for android.
#103

This package has slightly outdated camera and ml_vision packages.
I could not definitely tell where is the root cause of memory leak.//

There is no much hope for now that this package will be updated...
The easiest way is to copy all the code to your project and adjust according to your needs.

[jaumard]

In fact the leak is probably the usage of both camera and ml_vision, because the frame is going from native camera to dart, then go back to native code on ml_vision to process. I think it's this frame process that give us the leak. And there is currently no way to fix that except doing everything in native.

But if you actually find an easy fix I'll gladly review and merge it. But from what I have search I didn't find any one and I don't have time to dig more

[vasilich6107]

Vote for the issue
flutter/flutter#60409 (comment)