search

flutter-mapbox-gl / maps

A Mapbox GL flutter package for creating custom maps
Other
1.04k stars 502 forks source link

Stream of: setVertexArrayObject: set vao to .. (..) 100 ... #93

Open skinkie opened 5 years ago

skinkie commented 5 years ago

When developing and running the application I see an ocean debug messages flying by in the form of setVertexArrayObject: set vao to .. (..) 83 ...

I wonder a few things about this. I would expect that if there is no screen interaction the last rendered state would be taken, and no updates to the screen are executed, the debug stream suggests an updating window.

This error message is rather, verbose, and I can't find it in this repository, any suggestions?

tobrun commented 5 years ago

Do you have any information on the used device? Do you see this when running the normal Android SDK? (eg. Mapbox demo app in play store)

skinkie commented 5 years ago

@tobrun even better: the emulator :)

moopat commented 5 years ago

I have the same problem using the Pixel 2 Emulator:

CPU/ABI: Google Play Intel Atom (x86)
Target: google_apis_playstore [Google Play] (API level 29)
Skin: pixel_2
SD Card: 512M
fastboot.chosenSnapshotFile: 
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: pixel_2
hw.lcd.width: 1080
hw.initialOrientation: Portrait
image.androidVersion.api: 29
tag.id: google_apis_playstore
hw.mainKeys: no
hw.camera.front: emulated
hw.gpu.mode: auto
hw.ramSize: 1536
PlayStore.enabled: true
fastboot.forceColdBoot: no
hw.cpu.ncore: 4
hw.keyboard: yes
hw.sensors.proximity: yes
hw.dPad: no
hw.lcd.height: 1920
vm.heapSize: 256
skin.dynamic: yes
hw.device.manufacturer: Google
hw.gps: yes
hw.audioInput: yes
image.sysdir.1: system-images/android-29/google_apis_playstore/x86/
showDeviceFrame: yes
hw.camera.back: virtualscene
hw.lcd.density: 420
hw.arc: false
hw.device.hash2: MD5:55acbc835978f326788ed66a5cd4c9a7
fastboot.forceChosenSnapshotBoot: no
fastboot.forceFastBoot: yes
hw.trackBall: no
hw.battery: yes
hw.sdCard: yes
tag.display: Google Play
runtime.network.latency: none
disk.dataPartition.size: 6442450944
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes

It spams the log very aggressively, causing an EOF error in Logcat, so that I cannot use Logcat at all while the map is displayed. I don't see these logs when running the demo from the Play Store on a real device, maybe the logs are only printed in debug builds.

kleeb commented 4 years ago

Definitely a must have to disable this 

D/eglCodecCommon(13088): setVertexArrayObject: set vao to 1363 (1363) 17301 5963
...
m0nac0 commented 4 years ago

I'm not sure whether this is a bug with the plugin, as a similar issue has been described at flutter with a webview. Would be interesting to know which Flutter and Android versions you are experiencing this on, and if downgrading either of solves the issue.

kleeb commented 4 years ago

The latest Flutter, Android 9.0. Downgrading to 8.1 helps. Haven't checked yet on 10

m0nac0 commented 4 years ago

What flutter channel are you on? And if you're running anything later than flutter 1.12.13+hotfix.5, could you please try that version temporarily? I'm asking because the person who opened the issue I mentioned above described that downgrading flutter to 1.12.13+hotfix.5 solved the issue for them.

pomarec commented 4 years ago

Same problem :

This leads to a full CPU usage aswell

pomarec commented 4 years ago

This is not happening on API 27 nor API 29

pomarec commented 4 years ago

Perhaps related : https://stackoverflow.com/questions/60299236/

YegorMedvedev commented 4 years ago

Getting the same issue on API 29. Did anyone found a workaround so far?

jmealo commented 4 years ago

@YegorMedvedev: I'm starting to investigate a workaround/fix for this issue. I'll circle back and tag you if I find a fix.

iwo commented 4 years ago

@jmealo and progress on this issue? Is there any additional information you need?

Protofall commented 4 years ago

A fix would be very helpful, currently finding my own output is like finding a needle in the haystack. I'm also on an emulated Android API 29.

tobrun commented 4 years ago

I believe this is a emulator only issue on Android, with the way the egl context gets created. Let us know if you have seen this on an actual device though!

iuliuh commented 3 years ago

Having the same problem on the Pixel API 28 emulator.

edofritz commented 3 years ago

Simple, exclude log !setVertexArrayObject

skinkie commented 3 years ago

Simple, exclude log !setVertexArrayObject

So you would accept that internally the functional logging is actually taking place?

edofritz commented 3 years ago

Simple, exclude log !setVertexArrayObject

So you would accept that internally the functional logging is actually taking place?

you're right, I can't see the other logs because of this.

kleeb commented 3 years ago

any news ?

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

skinkie commented 2 years ago

Keep open.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

skinkie commented 2 years ago

Keep open.

battlecook commented 2 years ago

any news ?

youssefgh commented 1 year ago

I upgraded my emulator from API 28 to API 31. and that fixed the high cpu/crashing of vscode Now i only get this log that prints every 1s while moving the map

D/EGL_emulation( 8754): app_time_stats: avg=19.11ms min=11.98ms max=57.92ms count=52

But you can remove it by putting "!D/EGL_emulation" in the debug console filter