I’m trying to display 6 NFT markers on one page that trigger videos. With 2 markers, everything works fine, but using more causes slow loading and occasional crashes.
hey brilliantcoder39, this is super interesting – i stumbled upon similar issues and it made me wonder if the real culprit might be the way the app is handling the marker detection after the 2-markers threshold. i experiemced that sometimes when too many markers are active at once, the event loop gets overloaded because each marker renders it own video stream or similar, which can lead to slow downs and crashes.
have u tried maybe running some profiling to see if there are any memory spikes or if some marker events might be interfering with each other? i also wonder if maybe combining or lazy-loading the video triggers when they come into view could be a solution. what platform or framework are you using? sometimes a slight tweak in how resources are allocated or updating only visible markers might save a lot of processing load.
what do you think might be the best approach on your end? love to hear more about your setup and any tests you might have run so we can swap ideas!
hey, i got a similar issue and noticed many live vid streams can overwhelm the system. maybe try unloading markers not in view or turning off unused listeners to save resources. might also help to reduce video resolution a bit. cheers!
Based on my experience, one potential improvement was to modify the detection logic so that video playback initialization occurred only when a marker was clearly in view. In my project, the system struggled to keep up with the multiple live video streams once several markers were active at the same time. After thorough profiling, I identified that the marker detection algorithm was causing redundant computations. Refactoring the code to limit active markers in focus and reducing the event listener overhead resulted in significant performance gains, reducing both loading times and crashes considerably.
hey folks, really interesting thread! i was thinkin if the issue could be tied to how the markers and vid streams are loaded at the same time. maybe the system gets overwhelmed since all of them try to fire up concurrently? i once dealt with a similar problem by scheduling the initialization in small delays so not everything started at once. also, have u looked into using something like a webworker to offload some of the processing, or even a throttling mechanism for marker detection? it might also be worth checking if there’s any chance of overlapping events causing extra work. what kind of debugging have u tryed so far? would love to get more insight into how the markers are managed in your setup and if any tweaks in order of operations helped at all!
hey, maybe try lazy load for markers so videos only trigger when near view, not all at once. this might ease the cpu load and keep overlapping events at bay. hope that helps, cheers!