Skip to main content

Android Exception trying to open a new Activity - Surface::lock failed, already locked



When I try to open a new activity on a button press i get an Exception :







01-19 14:55:08.327: E/Surface(15454): Surface::lock failed, already locked

01-19 14:55:08.327: E/SurfaceHolder(15454): Exception locking surface

01-19 14:55:08.327: E/SurfaceHolder(15454): java.lang.IllegalArgumentException







I have a game that draws on a surfaceview canvas with a thread, that runs with the main process, I'm trying to open a new dialog box for input and nothing worked so I'm simply trying to open a new Activity that will Exception, I'm using the lock and unlock and well synchronized, I tried stopping the thread and even placing a couple of views. Any help is good Thanks.


Comments

  1. I expect your rendering thread is locking the surface after onPause() is called. Don't do that.

    In your Activity's onPause() you should tell your rendering thread to wait (outside the canvas lock/unlock) and then let it run again in onResume().

    A simple approach to doing this would be to create the rendering thread in onResume(), and then in onPause() signal that it should exit (maybe by setting a boolean value read in the thread loop) and then also wait for it to exit (via Thread.join()) before returning from onPause().

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex