Copy link to clipboard
Copied
Casino Game Maker is a Class III casino gaming manufacturer. It manufacturers gaming equipment for the Asian, North American, and Tribal markets. The platform that all our games are deployed on use Abode AIR, Adobe Stage3D, the Starling framework, and Awa 3D. Since the target is running in a Casino environment, it is required to be on 24/7. It is entirely possible for it to run for months or years before being turned off.
When running our platform for a period longer than 25 days, the Adobe AIR graphics component locks up. We believe that the reason behind this is because of a rollover of some timer like getTimer. If getTimer or an int is used for rendering, it will rollover at 2147483647 milliseconds. This is just shy of 25 days (24.86).
We have ran various tests using Starling only, Away3D only, Starling and Away3D, with all tests crashing at the 25 day mark. Since Starling and Away3D are open source, we have made adjustments to these code bases to prevent those components from crashing. However, we have no control over AIR and Stage3D and are unable to make any changes.
We have ran various longevity tests using Starling only, Away3D only, Starling and Away3D, with all tests crashing at the 25 day mark. Since Starling and Away3D are open source, we have made adjustments to these code bases to prevent those components from crashing. However, we have no control over AIR and Stage3D and are unable to make any changes.
Copy link to clipboard
Copied
We vote to get this problem fixed. getTimer need to return Number value.
One more bug report: Bug#4134873 - All graphics stop after about 25 days.
Copy link to clipboard
Copied
Hi,
Thanks for reporting this issue. We will look into it.
Copy link to clipboard
Copied
Thank you for looking into it. If you need anymore information or support, please let me know.
Copy link to clipboard
Copied
Hi,
Any news about fix this?