User posts pedwards
12 August 2017 15:39
Good to know, thanks for looking into it. Are you able to give an estimate for when you may be able to look into it and potentially submit a fix? We have a deliverable in a few weeks for a product configurator type project so any information you can give is highly appreciated.
11 August 2017 14:51
I've put together a simple project that reproduces the issue. You can download it here: https://drive.google.com/open?id=0B_nuwEOI7MTkQlp0S0RsdmExSXc
The issue is specifically occurring on the IPhone 6 on safari, it may be ocurring on other browsers as well. There are three scenes with different textures, click the buttons to change the scenes. I'm writing out the amount of consumed texture memory as reported by blend4web which appears to be fine, but if you inspect the amount of memory consumed on the device in the safari dev tools it keeps increasing as the scenes are swapped. Eventually when the memory consumption is high enough it will crash the browser and the site is reloaded.
Also just to note these aren't the textures or environments I'm using in our application, I just chose these large textures to show the issue.
The issue is specifically occurring on the IPhone 6 on safari, it may be ocurring on other browsers as well. There are three scenes with different textures, click the buttons to change the scenes. I'm writing out the amount of consumed texture memory as reported by blend4web which appears to be fine, but if you inspect the amount of memory consumed on the device in the safari dev tools it keeps increasing as the scenes are swapped. Eventually when the memory consumption is high enough it will crash the browser and the site is reloaded.
Also just to note these aren't the textures or environments I'm using in our application, I just chose these large textures to show the issue.
10 August 2017 03:11
I'm working on an application that has several environments which are swapped in and out by calls to data.unload() and data.load(). This is working except that b4w doesn't seem to be releasing texture memory when an environment is unloaded. Debugging the memory usage shows it increasing as new scenes are loaded, but not decreasing when they are unloaded. This is causing browsers on some mobile devices to crash once they've swapped between several environments. Any ideas on what might be causing this?
28 July 2017 10:58
I'm working on a 3d app that is split between multiple scenes. I have a single master scene that contains common objects like the camera object, and several environment scenes that each contain their own lights. In my app I'm loading the master scene with scenes.load() first, and then loading one of the environment scenes. The trouble I'm having is that the b4w runtime isn't loading the lights from any scenes loaded after the initial scene. Is it possible to load the lights from my environment scenes?