# Does it make sense to keep BitmapData globaly locked

**URL:** https://forum.kirupa.com/t/does-it-make-sense-to-keep-bitmapdata-globaly-locked/332116
**Category:** flash
**Created:** [February 4, 2014, 10:49pm UTC](https://forum.kirupa.com/t/does-it-make-sense-to-keep-bitmapdata-globaly-locked/332116 "2014-02-04T22:49:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![psykovsky](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/psykovsky/32/1386_2.png) [@psykovsky](https://forum.kirupa.com/u/psykovsky)
#### Post date: [February 4, 2014, 10:49pm UTC](https://forum.kirupa.com/t/does-it-make-sense-to-keep-bitmapdata-globaly-locked/332116/1 "2014-02-04T22:49:44Z")

</div>

[SIZE=4][FONT=georgia]Hello,  
I’m making an app that applies various effects on live cam feed - that’s a lot of _BitmapData_ manipulations.  
So my question is - does it make sense to lock all _BitmapData_ objects that never show on the screen [COLOR=#696969]_(FX manipulation layers)_[/COLOR] for performance boost and only locking/unlocking _BitmapData_ that actually goes on the screen.

If _BitmapData_ objects aren’t in the display list, does [COLOR=#0000ff]_lock()_[/COLOR] do anything at all?

Thanks in advance![/FONT][/SIZE] :cyclops:
