ImageSegmenter callback not called on Chrome, but working in Edge

[RajaniPriya19]

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)

Yes

OS Platform and Distribution

Windows 11 Enterprise

MediaPipe Tasks SDK version

"mediapipe/tasks-vision": "^0.10.13"

Task name (e.g. Image classification, Gesture recognition etc.)

Image segmentation in web

Programming Language and version (e.g. C++, Python, Java)

Javascript

Describe the actual behavior

Callback function is not called by ImageSegmenter's segmentForVideo function, hence results are not displayed. But working fine in edge browser

Describe the expected behaviour

Callback function should have been called ImageSegmenter's segmentForVideo with result

Standalone code/steps you may have used to try to get what you need

I am using ImageSegmenter "segmentVideo" function to detect human in each video frame. Code reference is taken from here: https://codepen.io/mediapipe-preview/pen/xxJNjbN
ImageSegmenter object is created using "createFromOptions" function. Model used is "deeplab_v3.tflite" and "GPU" delegate is used. I have written my own callback function.
Callback function is itself not called by ImageSegmenter, when code is executed in Chrome browser. But it is working as expected in Edge browser. A warning is displayed in both Chrome and Edge browser "Maximum number of pooled buffers reached. Consider increasing MultiPoolOptions.keep_count.

Other info / Complete Logs

Warning is displayed in both Chrome and Edge browser "Maximum number of pooled buffers reached. Consider increasing MultiPoolOptions.keep_count.

[kuaashish]

Hi @RajaniPriya19,

Could you please provide the complete error logs and the standalone code to help us replicate and understand the issue better?

Thank you!!

[github-actions[bot]]

This issue has been marked stale because it has no recent activity since 7 days. It will be closed if no further activity occurs. Thank you.

[eyaler]

running the example: https://codepen.io/mediapipe-preview/pen/xxJNjbN

when changing the versions from 0.10.2 to 0.10.14, i get:

iframeConsoleRunner-6d8bf8b4b479137260842506acbb12717dace0823c023e08b96360e60b0840d9.js:1 W0602
14:00:32.484000 1880752 reusable_pool.h:143] Maximum number of pooled buffers reached. Consider increasing MultiPoolOptions.keep_count
(anonymous) @ iframeConsoleRunner-6d8bf8b4b479137260842506acbb12717dace0823c023e08b96360e60b0840d9.js:1
custom_dbg @ vision_wasm_internal.js:9
custom_emscripten_dbgn @ vision_wasm_internal.js:9
$func13093 @ vision_wasm_internal.wasm:0x6f5421
$func5938 @ vision_wasm_internal.wasm:0x3a1122
$func3463 @ vision_wasm_internal.wasm:0x1b13b8
$func285 @ vision_wasm_internal.wasm:0xfa05
$func8190 @ vision_wasm_internal.wasm:0x5293b9
$func8399 @ vision_wasm_internal.wasm:0x52adf8
$func9843 @ vision_wasm_internal.wasm:0x53b476
$func3254 @ vision_wasm_internal.wasm:0x195067
$func994 @ vision_wasm_internal.wasm:0x5ca91
$func556 @ vision_wasm_internal.wasm:0x2e70c
$func11601 @ vision_wasm_internal.wasm:0x62adc8
$func12141 @ vision_wasm_internal.wasm:0x6419a2
$func10281 @ vision_wasm_internal.wasm:0x587abf
$func3200 @ vision_wasm_internal.wasm:0x18c0f5
$func3294 @ vision_wasm_internal.wasm:0x1a1448
$Pe @ vision_wasm_internal.wasm:0x41dcbf
Module._waitUntilIdle @ vision_wasm_internal.js:9
finishProcessing @ tasks-vision@0.10.14:7
finishProcessing @ tasks-vision@0.10.14:7
th @ tasks-vision@0.10.14:7
nh @ tasks-vision@0.10.14:7
Na @ tasks-vision@0.10.14:7
predictWebcam @ pen.js?key=pen.js-7b3d2e49-ff96-1111-5d17-dc7191e194d5:174

[kuaashish]

Hi @eyaler,

Could you please raise a new issue with a complete description of the problem you are facing, along with all necessary details so we can reproduce the issue on our end?

Additionally, @RajaniPriya19, if this issue persists, could you provide the complete details to help us reproduce and understand the problem? Thank you.

[eyaler]

@kuaashish, AFAICT this is exactly the same issue that @RajaniPriya19 reported, running the same code, where I tested also on 0.10.14 (the original report is 0.10.13), and I have provided the logs you've requested.