[x3d-public] Bad interactions between X3DOM and X_ITE. Small demo

[John Carlson]

I finally have a small demo which shows bad interactions between X3DOM and X_ITE that isn’t reliant on any of my libraries.  Can someone look at this to see if

1. I am doing something wrong
2. It can be fixed

Click on the buttons in different orders between reloads to see different behaviors.  If you click on the X_ITE buttons first, then boxes and spheres will appear.  If you click on X3DOM button first, then X_ITE buttons won’t work all the way (I have seen cases where 2 shapes appear).   I believe the more you load the X3DOM button, but fewer X_ITE scenes will appear, indicating that X3DOM is not releasing resources, but I’m not sure.   That requires further testing.

If we can fix this case, I might have a second case, depending on whether the first case fix fixes the second case or not.

I have duplicated this problem in Firefox.

Yes, I am aware of limited WebGL contexts.  I believe this problem shows up if you have 2 X3DOM canvas and 2 X_ITE canvas after 5 or so reloads of each canvas.

Basically, X3DOM is starving X_ITE, X3DOM needs to stop hogging and X_ITE needs to develop some offenses and defenses.

Thanks,

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180320/ad7d6b83/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: box.x3d
Type: application/octet-stream
Size: 794 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180320/ad7d6b83/attachment-0001.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180320/ad7d6b83/attachment-0003.html>