LifeViewer load times

[unname4798]

Despite running Chrome 132 on Android 9, I still get LifeViewer Standard instead of Pro; whatever problem happened?

The Pro is in beta testing only.

[rowett]

On my laptop, the displayed page scan time varies around 3.4 to 4.4 seconds.

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.

From my measurements, the real clock time appears to be roughly 4 to 7 seconds.

The page scan timing should be accurate. You're probably seeing additional time taken by the browser or the operating system.

I tried clicking "Launch" on the viewer. Launching takes around 10 to 12 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.

[rowett]

Despite running Chrome 132 on Android 9, I still get LifeViewer Standard instead of Pro; whatever problem happened?

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]

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.

I don't know what's exactly to "hard refresh" the browser. The help stills shows build 1238 - am I missing something?

[confocaloid]

On my laptop, the displayed page scan time varies around 3.4 to 4.4 seconds.

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.

Build 1239, the displayed measurement varies between 2.9 and 3.1 seconds.

Refreshing that page while it is opened, causes a sequence of error messages:

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

[rowett]

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.

I don't know what's exactly to "hard refresh" the browser. The help stills shows build 1238 - am I missing something?

See here.

[rowett]

Build 1239, the displayed measurement varies between 2.9 and 3.1 seconds.

Great, thanks for the data. This shows that memory is certainly a factor.

Refreshing that page while it is opened, causes a sequence of error messages:

Yes, this is expected on this experimental build.

[rowett]

I've added Safe Mode to LifeViewer to better deal with low memory devices. See here for how to use.

When a device is low on memory it starts using the page file (swapping memory out to storage) and this tanks application performance.

Here on the forum Safe Mode stops LifeViewer from adding SHOW IN VIEWER links to patterns using [[ MAXGRIDSIZE 14 ]]. This improves page scan time and saves memory.

On the Wiki it allows Thumbnails with [[ MAXGRIDSIZE 14 ]] but doesn't allow them to be launched. So you still get to see the pattern but can't use more memory by opening it.

Instead, hovering over the Thumbnail will display Copy and clicking it will copy the pattern RLE to the clipboard. You can disable the copy functionality with the [[ NOCOPY ]] script command.