The Pro is in beta testing only.b-engine wrote: February 7th, 2025, 11:53 pm Despite running Chrome 132 on Android 9, I still get LifeViewer Standard instead of Pro; whatever problem happened?
Thanks. Please try again (same link) but please hard refresh your browser to ensure you get build 1239. I've adjusted the memory usage to see if it helps.confocaloid wrote: February 7th, 2025, 11:46 pm On my laptop, the displayed page scan time varies around 3.4 to 4.4 seconds.
The page scan timing should be accurate. You're probably seeing additional time taken by the browser or the operating system.confocaloid wrote: February 7th, 2025, 11:46 pm From my measurements, the real clock time appears to be roughly 4 to 7 seconds.
Yes I've not optimized that yet. However it's still interesting data. That might indicate that your device is very low on memory.confocaloid wrote: February 7th, 2025, 11:46 pm I tried clicking "Launch" on the viewer. Launching takes around 10 to 12 seconds.
Not sure. Please try here and hard refresh the browser. Make sure Help shows build 1239. If so and Pro is not available then it should show an error message. Let me know.b-engine wrote: February 7th, 2025, 11:53 pm Despite running Chrome 132 on Android 9, I still get LifeViewer Standard instead of Pro; whatever problem happened?
I don't know what's exactly to "hard refresh" the browser. The help stills shows build 1238 - am I missing something?
Build 1239, the displayed measurement varies between 2.9 and 3.1 seconds.rowett wrote: February 8th, 2025, 9:23 amThanks. Please try again (same link) but please hard refresh your browser to ensure you get build 1239. I've adjusted the memory usage to see if it helps.confocaloid wrote: February 7th, 2025, 11:46 pm On my laptop, the displayed page scan time varies around 3.4 to 4.4 seconds.
Code: Select all
Failed to allocate 512 element Uint8 array for PatterManager.ruleArray
TypeError: va.memory is null
Failed to allocate 512 element Uint8 array for PatterManager.ruleArray
TypeError: va.memory is null
Failed to allocate 512 element Uint8 array for PatterManager.ruleArray
TypeError: va.memory is null
Failed to allocate 512 element Uint8 array for PatterManager.ruleArray
TypeError: va.memory is null
Failed to allocate 32 element Uint16 array for Life.blankRow16
TypeError: va.memory is null
Failed to allocate 2 element Uint16 array for Life.blankTileRow
TypeError: va.memory is null
Failed to allocate 512 element Uint8 array for Life.blankColourRow
TypeError: va.memory is null
Failed to allocate 256 element Uint32 array for Life.pixelColours
TypeError: va.memory is null
Failed to allocate 21 element Uint8 array for Life.nextStateExtended
TypeError: va.memory is null
Great, thanks for the data. This shows that memory is certainly a factor.confocaloid wrote: February 8th, 2025, 9:51 am Build 1239, the displayed measurement varies between 2.9 and 3.1 seconds.
Yes, this is expected on this experimental build.confocaloid wrote: February 8th, 2025, 9:51 am Refreshing that page while it is opened, causes a sequence of error messages: