Fixed
Status Update
Comments
mc...@google.com <mc...@google.com> #2
To make life even more bizarre, I ran into another situation where camera.open()
worked in the sense that it didn't hang as in the previous example, but a following
camera.setParameters() did hang:
Log.i("OIC", "JUNKcam5");
try { camera.setParameters(parameters); }
catch (Exception e) { Log.e("OIC", e.getMessage(), e); }
Log.i("OIC", "JUNKcam6");
then only gave as output
JUNKcam5
In this case too, the built-in camera app would just hang with a black screen, and I
had to power off the phone to get back.
Regards
worked in the sense that it didn't hang as in the previous example, but a following
camera.setParameters() did hang:
Log.i("OIC", "JUNKcam5");
try { camera.setParameters(parameters); }
catch (Exception e) { Log.e("OIC", e.getMessage(), e); }
Log.i("OIC", "JUNKcam6");
then only gave as output
JUNKcam5
In this case too, the built-in camera app would just hang with a black screen, and I
had to power off the phone to get back.
Regards
[Deleted User] <[Deleted User]> #3
This issue is assigned to an engineer for further evaluation
cs...@google.com <cs...@google.com> #4
Great. I still regularly run into this problem while developing my camera app, say
once or twice a day. It looks a bit like the camera does not always get released, and
once detached from a given app (when the app crashes or perhaps leaks some context
when it exits normally) no app can connect to it anymore, including my own app. I
still only know of the power cycle to get the camera back.
once or twice a day. It looks a bit like the camera does not always get released, and
once detached from a given app (when the app crashes or perhaps leaks some context
when it exits normally) no app can connect to it anymore, including my own app. I
still only know of the power cycle to get the camera back.
[Deleted User] <[Deleted User]> #5
Could you attach the output of adb bugreport or at least adb logcat -v threadtime the
next time this happens? This'll assist with diagnosing the issue. Thanks.
next time this happens? This'll assist with diagnosing the issue. Thanks.
Description
when clicking on the map, we have code that shows a map with tool tips in a popup.
Up until about 2 releases of chrome ago, it worked fine, but now in both Chrome 45.0.2454.101 (64-bit) and Chrome Canary 47.0.2521.0 canary (64-bit) the tiles do not show. There are no JS errors on the page,
On every other browser this still works fine.
There have been no source code changes at our end, I think this coincides iwht the september 15th release of 3.22 of the api