cannot read properties of undefined - description

[flatsiedatsie]

I'm trying the Phi3.5 vision demo, but got the error below.

I proceeded to wrap that bit of code in if(K.adapterInfo){ ... }

And then it started working.

• Macbookk Pro M1
• Brave browser

Another thing I then ran into: I'm not allowed to use relative image paths?

[flatsiedatsie]

I've created a quick demo on Github pages:

https://flatsiedatsie.github.io/web_llm_vision/

and then I created a Reddit post about your awesome work here:

https://www.reddit.com/r/LocalLLaMA/comments/1fnjnkc/webllm_has_added_support_for_its_first_vision/

[CharlieFRuan]

I haven't ran into this issue yet, but below are some info.

The adapterInfo is defined here:
https://github.com/tqchen/tvm/blob/412aec4e2df8f01ee15f3165d9f740af5190866d/web/src/webgpu.ts#L27-L31

The adapterInfo is populated here:
https://github.com/tqchen/tvm/blob/412aec4e2df8f01ee15f3165d9f740af5190866d/web/src/webgpu.ts#L119-L133

Specifically, GPUAdapter.info (i.e. the adapterInfo) is documented here: https://www.w3.org/TR/webgpu/#gpuadapter

I am not very sure why info could be undefined. Though there is indeed a related API deprecation on requestAdapterInfo() from the WebGPU side, where we adjusted this way: apache/tvm#17371

[CharlieFRuan]

I wonder if it is because your browser still prefers requestAdapterInfo(). If not too inconvenient, could you try updating the browser or using a different browser to see if the same issue is observed? Thanks!

[flatsiedatsie]

Sure, I'll give it a try.

[flatsiedatsie]

I removed the checking code:

if(K.adapterInfo){    ...    }

And then enabled WebGPU on Safari. I saw the same error:

Line 27

[flatsiedatsie]

I just found out this is now interfering with all WebLLM inference, not just the Vision model.

[slash-under]

This issue affects me as well on Thorium (Chromium) 124 with an Nvidia GPU on Windows, and the proposed solution works for me. As far as the GPUAdapter reference goes, there are some missing members, including GPUAdapterInfo.

[CharlieFRuan]

Thanks for all the info, I'll fix it today

[CharlieFRuan]

Though I believe using the latest chrome should fix it; but I'll make sure we are backward compatible

[slash-under]

The issue persists with the latest Thorium (126) but it looks like there have been further releases upstream....

Edit: there are no issues when using a nightly build of Chromium: 131.0.6742.0

[CharlieFRuan]

Thanks for the info, fix is under the way