Developers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sonnykr
Visitor

Re: roTextureRequestEvent getBitmap() fails

That's true, I never expected calling GetBitmap() multiple times would cause a crash. May be this should be added to the documentation. Especially since it causes Roku to restart.
Tags (1)
0 Kudos
RokuKC
Roku Employee
Roku Employee

Re: roTextureRequestEvent getBitmap() fails

"sonnykr" wrote:
That's true, I never expected calling GetBitmap() multiple times would cause a crash. May be this should be added to the documentation. Especially since it causes Roku to restart.


Issue confirmed. Thanks for the bug report.
Tags (1)
0 Kudos
sonnykr
Visitor

Re: roTextureRequestEvent getBitmap() fails

"RokuKC" wrote:
"sonnykr" wrote:
That's true, I never expected calling GetBitmap() multiple times would cause a crash. May be this should be added to the documentation. Especially since it causes Roku to restart.


Issue confirmed. Thanks for the bug report.


Oh cool. Thanks RokuKC!
Tags (1)
0 Kudos
EnTerr
Roku Guru

Re: roTextureRequestEvent getBitmap() fails

"TheEndless" wrote:
Interesting.. you're calling GetBitmap() three times in that code, and it doesn't blow up until the last one. I wouldn't expect it to ...

In practice it was getting called only 2x - because of the short-circuiting of the OR - so it was bombing on the 2nd call to getBitmap(). It would be disconcerting if it was err-ing on the 3rd call but now is just a regular bug, phew 8-)

Also, i don't think there is type()="bitmap" ever, is there? I trust when getBitmap() <> invalid, it's always roBitmap.
Tags (1)
0 Kudos
Community is Being Upgraded!

We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. Read more here.

Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 19th and you may notice reduced functionality. In the meantime, for additional assistance, visit our Support Site.

We're sorry for this disruption — we’re excited to share what’s next!