IssueTracker

Disabling all extensions does not fix the problem.

Enabled log-level=0 and got the following:

$ google-chrome --enable-logging --log-level=0
[20397:20397:1383124398002:ERROR:chrome/app/chrome_dll_main.cc(247)] GLib-GObject: instance of invalid non-instantiatable type `(null)'
Segmentation fault

Adding debug log.

Do you have crash reporting enabled?  If so, a crash id should be dumped, and if you give that to us, then we can look up what caused the crash.

My client_id appears to be B7776A6E-F752-1E5B-E46B-ACD5F961EE30.

I see crash_count: 0, but since I've enabled it I've gotten it to crash twice.

Seems to happen immediately after geolocation is finished.

I only see 2 browser crashes from your client id:

Stack trace:

Thread 0 *CRASHED* ( SIGSEGV @ 0x00000020 )
0xb6c306ca      [libdbus-glib-1.so.2.1.0        + 0x0000d6ca]  
0xb6c30be4      [libdbus-glib-1.so.2.1.0        + 0x0000dbe4]  
0xb6c324f9      [libdbus-glib-1.so.2.1.0        + 0x0000f4f9]  
0xb6c2f17e      [libdbus-glib-1.so.2.1.0        + 0x0000c17e]  
0xb6c07790      [libdbus-1.so.3.4.0     + 0x0001d790]  
0xb6bf73c5      [libdbus-1.so.3.4.0     + 0x0000d3c5]  
0xb6bf9991      [libdbus-1.so.3.4.0     + 0x0000f991]  
0xb6c2a92c      [libdbus-glib-1.so.2.1.0        + 0x0000792c]  
0xb705b5e4      [libglib-2.0.so.0.2400.1        + 0x0003b5e4]  
0xb705f2d7      [libglib-2.0.so.0.2400.1        + 0x0003f2d7]  
0xb705f4b7      [libglib-2.0.so.0.2400.1        + 0x0003f4b7]  
0x08707d34      [chrome         - base/message_pump_glib.cc:195]        base::MessagePumpForUI::RunWithDispatcher(base::MessagePump::Delegate*, base::MessagePumpForUI::Dispatcher*)
0x0870796f      [chrome         - ./base/message_pump_glib.h:59]        base::MessagePumpForUI::Run(base::MessagePump::Delegate*)
0x086e00f3      [chrome         - base/message_loop.cc:214]     MessageLoop::RunInternal()
0x086e0161      [chrome         - base/message_loop.cc:617]     MessageLoopForUI::Run(base::MessagePumpForUI::Dispatcher*)
0x08073625      [chrome         - chrome/browser/browser_main.cc:198]   BrowserMain(MainFunctionParams const&)
0x0806cb4a      [chrome         - chrome/app/chrome_dll_main.cc:861]    ChromeMain
0x0806cf5f      [chrome         - chrome/app/chrome_exe_main_gtk.cc:50]        

Are they the same? I can reproduce it a few more times if you'd like.

I'm guessing geolocation tries to initialize glib-dbus, which is crashing, possibly due to a race condition. Perhaps r50652 fixes this, or cause the crash to happen sooner?

[Empty comment from Monorail migration]

twitter.com appears to have removed the geotagging feature from the web interface. At least, my colleague can no longer find it (I've never seen it before)
I've tried on some other websites (e.g. maps.google.com/maps/m) and I can't recreate this there. Would be interesting to know if anyone else can?
(This is on the same chrome version)

Btw I'm out for a week now, so if this is urgent we may need someone else to look into it.

One more question, Ian.
You mention: "Seems to happen immediately after geolocation is finished."
However, from the log file attached, I don't see any evidence of geolocation working (but this maybe because you already had another tab open that was also using geolocation and so pre-cached the location?)

Could you clarify how you know geolocation is finished? What is the visible indicator on the website?

Cheers

I seem to have been chosen for A/B geolocation testing on twitter as others have mentioned not getting the geo feature on their twitter pages, too.

The way geolocation on twitter (at least for me) is:
1. after logging in and hitting http://twitter.com, a small link with the text "Add your location" and a crosshairs next to it appears directly underneath the "What's Happening" text box.
2. clicking the link requests geolocation from Chrome (Chrome asks for permission and shows the crosshairs in the URL bar). The twitter.com UI switches to a "Getting your location..."
3. when Chrome comes back with a location, the UI element changes to a "in X" link (where X is the best guessed location). If you click on the "in X", a dropdown list of nearby cities and businesses shows up. Clicking on one specifies that location for your tweet.

I said that it seems to happen immediately after geolocation because both crashes that I had yesterday occurred at step 3 when the UI element changed to the link. I did not have to click on anything on the page to get it to crash.

Great, many thanks for the clarification.

Could you try another site or two using geolocation and see if it happens
there?
maps.google.com/maps/m
http://www.google.com/search?q=geolocation+demo

So it looks like the twitter geotagging feature is only available in the US right now
http://twitter.zendesk.com/forums/26810/entries/122236
> Please note that this feature is currently only available for US users - Twitter's @support account will let you know when it's available in other countries.

I connected to twitter via US based proxy, was presented with the geotagging UI, and sucessfully posted some tweets. No crash.
This is on Ubuntu 10.4, and Chrome 6.0.437.3 (Official Build 50164) dev
I've got some passwords in the password manger (just in case this is kwallet interaction)

Ideas?

I tried the demos and it looks like geolocation works fine.

Vague idea:
- does this dev version have the kwallet D-Bus code enabled?
- if so, is this a repeat of http://crbug.com/40803 which we had on geolocation? i.e. kwallet is sometimes causing code to run on the main loop? Perhaps it needs the same work-around as was applied to geolocation.
(but hard to explain why twitter.com would be exposing this, when using the geolocation feature).

I just had it crash a couple more times. It's definitely not timed the same for every crash: sometimes geolocation works and I can click around other parts of twitter.com with no problem. It seems to happen more frequently when I sit on twitter for a few minutes doing stuff in other windows and then come back to the page.

I'm in the US, just updated to a recent version of Chromium (50687), and am on Mint 9 (Ubuntu 10.4).  I still have twitter crash all chromium tabs and windows about half the time when I go to my home page.

Evan, look at Joth's https://crbug.com/chromium/47319#c17.  It does seem like quite a coincidence that the password manager stuff recently went out and we're now seeing this crash.

If 50687 is crashing (as per https://crbug.com/chromium/47319#c19), then moving the dbus initialization to one place in startup in r50652 hasn't helped :(

HenrySchreinerIII: can you get a backtrace of the crash at all? (just to see if it's also dbus in there).

jorlow, joth: the password manager stuff is disabled normally isn't it without an explicit password-store command line option? (well maybe there's some initialization stuff that still runs ... I haven't looked)

For what it's worth, I have "Never save passwords" and "Enable AutoFill to make it easier to fill in forms" (but with no profiles created) checked.

[Empty comment from Monorail migration]

(whoops, it's already on dev channel, we should at elast prevent it from getting to beta)

[Empty comment from Monorail migration]

I'm having a similar issue on OSX 10.6.4 with Chrome 6.0.447.0.

Chrome does not crash but it will take 30-45 seconds from the load of the page until a location is loaded. The entire length of that time Chrome is almost completely frozen.

If I have Twitter configured to not automatically find my location the delay never happens. If I manually click "Add your location" the delay and freeze happens.

This bug is about Linux.  Can you open a separate one about the Mac issue?  It is plausible it has a different cause.

[Empty comment from Monorail migration]

Any updates on this?

I've been reticent to check twitter.com lately because I'm doing actual work... I just checked now and couldn't get it to crash. Same version, no changes on the system (haven't done any package upgrades). Twitter must have changed something on their side?

Not sure how to proceed with this one: this is the only report, and it's no longer happing.

I now notice the OP says using incognito windows stops the problem; there's very little reason that geolocation would stop crashing when in incognito, which leads me to think it is (was) something the javascript code was doing in response to receiving the geolocaiton result, rather than the result itself, that was causing this crash.

I can't get Twitter to crash anymore with 6.0.458.1 (Official Build 51742) dev. I would vote for marking this closed with the explanation that it was some external-to-Chrome interaction.

On my home laptop (which has been running dev builds too -- previously I thought I had it on beta) twitter never crashed.

As per the comments, Cannot reproduce.

Was only ever seen on one machine, and now can no longer be seen there either.

I came across this bug report and thought I should chime in.

I get this error in chromium on both a Windows machine and Ubuntu Lucid. It doesn't take down Chromium, but does crash the twitter tab - I load the twitter.com page and within 10 seconds or so, I get the window popping up saying the tab has crashed and I can either wait or kill the tab. Waiting just leads the page loading constantly, you can read the page, but it can't be scrolled. I use the Chromium updater tool on Windows and the daily build PPA on Linux, so both builds are pretty up-to-date.

I've been seeing this occur ever since I started using Chromium about a month ago. It does seem rather random though, it doesn't always happen...

@pathios, you maybe seeing another issue: 59913. That should now be fixed on the dev channel.

may this will help, I can get into twitter.com running chromium as root, this means a permissions problems isn't? but where?

I can confirm I also get this error but it resolves itself if I run my browser as root.

14.0.790.0 canary, just ran into the problem

14.0.792.0, openSUSE, same symptoms as https://crbug.com/chromium/47319#c37, 32bit and 64bit archs

Fedora 15, 64bit Chrome 12.0.742.112. Problem exists

I tried removing Site Data for twitter.com, but Chromium also crashed when trying to delete Web Database from UI as well. After that I went to ~/.config/chromium/Default and deleted the whole "databases" subdirectory. Upon deletion twitter.com works again. Therefore I guess there is some problem in the WebDB storage code.

14.0.825.0 under openSUSE seems to work

Fedora 15, fresh reload, recent update, latest chrome, 13.0.782.107, awww snap page when going to twitter.com.  twitter.com/about works, https://support.twitter.com/ works, even signing in here, but returning to profile, awww snap.  Tried clearing cache, cookies, etc.  Nope.

If you're encountering this on Fedora, it's https://crbug.com/chromium/81413.  I'd love it if you commented on the bug I filed with them: https://bugzilla.redhat.com/show_bug.cgi?id=710276 and asked them why they can't fix it.  ;)

(This bug is from July 2010.  If you are still encountering a problem with this specific bug, then please either star https://crbug.com/chromium/81413 if it applies to you, or open a new bug so your info isn't lost.)

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

This issue was migrated from crbug.com/chromium/47319?no_tracker_redirect=1

[Monorail components added to Component Tags custom field.]

Same problem here; Running a Nexus 5 bought yesterday. Using it as a company phone, encrypted, with all the different kinds of login disabled excepting PIN; I also have location, bluetooth, 3g and data disabled, . Have used Camera once and the  mm-qcamera-app process drained most of the battery in 6 hours from a full charge. Also charging takes forever (3% in 20 minutes). No additional apps for camera use since I am not taking pics with the phone very often. Please advise on resolution.

Regarding comment #51... I'm developing a rather advanced video engine for Android presently and thus am dealing with all sorts of camera issues including the mm-qcamera-daemon problem.  The problems seem definitely related to Qualcomm SoCs which are behaving badly in app lifecycle situations. To prevent issues for my test app / middleware it's necessary to of course shut down any connections to the camera via the camera API, but I've found that seemingly to get things to not hang sporadically the app must always manually call finish() for the Activity interacting with the camera. This means calling finish() when the home button is pressed and not let the Activity interacting with the camera linger even if release() is called on any active camera instance from the camera API.

While I can't authoritatively say this solves the symptoms to this problem I haven't seen any problems on Qualcomm based devices after making this change to my test app and I'm testing it all the time on the Nexus 5 presently. This of course is for developers of camera apps and not an end user / consumer solution.  There seems to be some interplay with the Activity lifecycle / OS / and Qualcomm camera service implementation that is definitely different than other Android devices w/ different SoC manufacturers. I tried to debug and do everything possible to avoid a manual call to Activity->finish() when leaving focus of my test camera app. That is the only thing that stopped camera issues on Qualcomm based devices.

Re #53 as long as you call "release()" for the camera; it doesn't seem to ever hang for me unless there was a violent crash.  Depending on the device, mm-qcamera-deamon may force close the connection after a period of time or may totally foobar the device until next restart.  This seems to be very device (possibly driver version) specific.

On the 2013 Nexus 7, using 25% or 1 core at 100% is absurd amount of cpu power just to draw the camera to the screen.  Either every reporting tool I can use is incorrectly reporting the cpu usage or something is seriously wrong with the qualcomm camera driver.

@ #54  My money is on a fubared Qualcomm camera driver & unstable MediaCodec implementation on Qualcomm SoCs as well.

Yeah, why I mention that I can't authoritatively claim calling finish() helps specifically with the symptoms posted in this issue it was definitely necessary for using MediaCodec on Qualcomm based devices. Unfortunately a start / stop / initialization cycle of MediaCodec crashes in certain situations on Qualcomm SoCs where it works on all others I've tested thus far and this crashing situation certainly triggers the "violent crash" scenario hence not reaching a call to "release" for the active camera instance reliably thereby further triggering the symptoms in this issue with mm-qcamera-daemon, etc. It's a big mess really from the dev side of things regarding side effects of clearly unstable / untested APIs.

For example one of the more exotic MediaCodec crash scenarios was recording a video in my app then hitting "home" going to MXPlayer to play the video and when returning to my camera app MediaCodec would hang and crash no matter what I did to properly set things up and of course just on Qualcomm based devices.  This doesn't occur if "finish()" is called when leaving my test app.

It's a bandaid that has thus far brought stability to my current camera / MediaCodec app efforts on all devices with no problems since I included it. Not ideal at all and kind of a pain, but less bad than crashes and the symptoms in this issue. I exhaustively tried everything else as far as control flow goes before resorting to the "finish" hack.

I'm in on this too. I use GN3 with stock ROM on AT&T. Phone heats, battery drains super fast, & this daemon process as at 51% of battery usage constantly. Rebooting the device seems to help, but it recurs.
Since the phone is useless in this state, I will be returning it within the hour.

Ever since I returned my phone to factory settings (a week or so ago), and
reinstalled all apps that I was using except for Greenify (or any of the
other "battery saving apps" that are out there), this problem has not
occurred.
I really suspect that a hard shutdown of camera-using apps will cause the
process to panic, and overrun the CPU.

Of course, this is just anecdotal, and it is a bug, the daemon should not
do this. Not using battery saving apps has solved my problem.

Same here with a GN3 stock rom.

This issue is killing my smartphone experience.

I have the same issue, some people said that this problem caused by yahoo messenger but i don't have it?
I hope someone find a way to fix it!

After I uninstalled Barcode Scanner my problem went away. But it seems like the problem can happen with a number of apps.

We have seen that debug traces gets overflowed with thousands of camera face detection events per second as soon as any app related to camera use is started. It is probably related to the above. This happens on Note 10.2 2014.
Turning face detection off has no influence.
This is a typical debug message:
E/mm-camera( 315): module_faceproc_client_send_info:1763] face_cnt 0
It is urgent to get this fixed.

Nexus 5, 4.2.2.

No face log-in. I don't know of any other apps that access the camera by itself.

I think my case may have been triggered by Waze when it was trying to detect a hand wave. Reboot seems to help.

It seems to be definitely triggered by apps that access camera. Not sure if this is an issue with the camera API usage practice or bug in the driver/daemon.

Try take a debug log and see if you also get the flood of face detection notifications.

I just got my first smartphone less then a week ago after giving up my old LG flip phone that I for 10 years. I got the Samsung Galaxy Note 3 and everything has been great up until this afternoon when I noticed the phone getting really warm to the touch and my battery plummeting down to nothing in a matter of an hour.  I noticed the mm-qcamera-dameon was at 66%. I had yahoo messenger on my phone and all was well with it. I tried to use it this evening but I couldn't get it to work now.  I did download a few apps today but have since deleted them in thinking they may have caused the problem.  I haven't used the camera since the first day I got the phone last week.  This is ruining my first smartphone experience really fast.  Also, my phone has been charging for the past 4 hours and it still is at only 76% in being charged.  My old phone only took about 2 hrs. max to charge up, if that.

On #51 and #61: The enormous flood of face detections start for any app using the camera. So, it is not directly related to any app.
And it starts regardless of if you have any face detection function activated in the app. It seems to be the face detection logic spinning free without any wait time between the detection scans. Or it gets triggered by some indication from the camera that there is a new image delivered to scan and that indication appears more than once per image. (Just guessing on these reasons )

On #53 You say you call finish() when you exit the app. But don't you have the problem while the app using the camera is running?
 

@65

It's hard to say if there is any extra drain on the battery during the operation of my app in normal conditions since my test app is a demo for rather intense OpenGL camera manipulation / video engine middleware. It's a bit of a battery hog to begin with given all that it is doing and I'm really working the GL pipeline in a way that I haven't been able to do with SoCs prior to Snapdragon 800 / Adreno 330, but "After Effects in your pocket" will do that!  

So, yes, indeed the device gets hot particularly around the camera itself at times.  I haven't had much chance to do a detailed analysis during runtime regarding battery usage or breakdown between my app / GL / potential camera service other areas, etc. I'll be able to tune and test things better once I get more recent devices to test with soon.

My older devices like the Galaxy Nexus on 4.3 don't have any problems except not being able to support nearly as much functionality due to an older GPU.

As mentioned in #55 I have to call finish() especially on Qualcomm SoCs to reset anomalies with MediaCodec that will crash in various strange and complex / indeterminate ways otherwise that  caused problems with the camera service / functionality when the app was not running or when restarting after sending the app into the background.  

As things go there area a lot of problems surrounding the camera functionality on the N5 / Android 4.3 & 4.4.x for devs and end users alike. It seems like things are stuck in a limbo phase between the next major revision of the camera APIs and everyone is going to suffer for a bit.

Hi, everyone!
This is for all, who are not developing but just want to get rid of this nuisance.

What I wrote in #50 about three weeks ago still works.

"Longterm tests" - meaning: start video recording and let it run until the battery is nearly down - with both remaining apps on the phone (Motorola stock app and LG Camera free)lead to a usage of mm-qcamera-daemon of about 7%, which is down to 2% after a few hours of normal usage and complete gone overnight.

Knock on wood that thiswill last, Good luck to all who will test on their phones!

Having the same issue, the process is taking up 68% of my CPU, a restart didn't help. Nexus 5 owner.

I solved by removing the camera shortcut from desktop. N5, Cataclysm ROM, franco kernel r33.

Noticed this same issue today. Using Nexus 5 32GB and did not start any camera apps in days. Suddenly this morning phone feels hot to touch and battery drained very fast. Most of it (60+ percent) spent on mm-qcamera-daemon process. Please elevate this issue, this is not minor, it's major battery drain and as far as I could find lot of people are having this happen. I don't use snapchat (seen some relating this issue to that app but nope in my case). Google, please fix, this is ruining my Nexus experience.

This is a very serious problem that needs attention.  My stock Nexus 5 is suffering daily from this issue and none of the ideas work.

i have same issue. i missed some of my important calls two days back .

[Comment deleted]

I've noticed this issue lately on my stock N5 and, while I haven't done any extensive testing, it seems coincidental that it happens after I take a picture and then share it to something. Facebook, gmail, etc.. Just the times that I am in the camera app and click the share function.  My guess is that it doesn't properly give the exit commands when that happens and my workaround will be to exit the camera app and then share manually from the photo viewer.  Again, haven't tested and don't have time at the moment, this is just a theory.  From reading what other people have posted on this it seems to be similar symptoms no matter what app they are posting to.

Same issue.
Dont use any video capture.
Bugs with the photoApp natively present on phone.

Have nexus 5 , Android 4.4.2

Happened to me this AM...battery dead overnight while sleeping.
Nexus 5 stock 32GB.
Lite user - both cell,camera & data.
I uninstalled Instagram (never used) & removed camera icon from Favorites tray.
Started using Watchdog Lite to monitor CPU usage offenders.
I hope this is a one time event.

GN3, same issues with battery getting hot, and draining very fast.
Not installed Snapchat, or Yahoo messenger.
Tried rebooting a number of times - no help, also removed camera icon from home screen, no help either.

Same issue here. Had my N5 since launch and today (2/21/14) was the first time this has happened. Took up 59% battery life and drained my phone with barely any usage. Please fix!

Same issue here. Battery is getting hot, no Snapchat or Yahoo messenger. Phone now charges slowly even after a reboot

My issue started after I connected my AT&T Note 3 to my computer and backed it up via the Samsung Kies 3 software. Kies must have done something during the backup. From my research, the problem resides in the external SD Card. I have a SanDisk 64 GB Class 10 micro and it must have went haywire during the Kies back up. I plugged my phone into my computer and backed up all the contents of my SD Card to a folder on the desktop. Then I went into the settings menu under General then Storage. I tried to format the SD Card. It said it was formatting but never actually deleted the pictures or video. So I unmounted the card popped it out of the phone and put it back in. Then I did the format again. This time it worked and all my files were deleted. This problem has happened to me before and then went away for a long while. The fix that worked for me was formatting micro SD card.

My Nexus 5 stock with 4.4.2 Kitkat, no roms or roots installed, running well from last November since last days ago, when the battery drain come to max level caused by the process above. I restart the phone many times without success, the camera is unusable and the phone has to be recharged in few hours.
This is not a small bug, but a serious problem that come to return many devices to the vendor and to cancel what we know as the Nexus Experience, please solve it ASAP.

Since a few days ago, I also have this Problem. I also don't use snapchat. Maybe it is a bug in the Google play services released a few days ago?

I am facing the same issue since yesterday. I have not installed any new app in the recent past.The mmq-camera-daemon is using 49% of the battery.
I do not have Instagram, Yahoo Messenger installed.
How to stop the mmq-camera-daemon? How to resolve this issue?
Please help

Put me down for having this problem crop up in the last 24 hours.  I've owned this Nexus 5 since release and have had no battery issues until now.  No snapchat or yahoo for me either.  55% of battery is being consumed by mm-camera-darmon and cut is pegged all the time.  

I am having this issue aswell on my Nexus 5 since yesterday. Had the Nexus 5 since launch and no major issues. This mm-qcamera-daemon only appeared in the battery stats today and it's used up 49% battery. Hardly got through 4 hours! Had to recharge. How can a process/issue like this come out of nowhere. Google really needs to look into this issue!!!

I am having the same issue on my nexus 5. Been seeing this issue the past couple of days. It's been draining my battery. Need a fix google!!

We need to start posting negative reviews on Amazon to get the attention of
the powers that be.

also was seeing this issue in recent days.  Have not seen it anymore after uninstalling skype.

Add me to the list of N5 owners with mm-qcamera-daemon sucking life out of battery at high rate.

Can we try to isolate the problem a bit better. My problem is #61, that a lot of extra CPU is wasted while an app is used that I want to run. So it is not exactly the same as all these reports about spontantaneous use of CPU for something camera related. But close enough to suspect that they have the same cause. It may be hardware related. Or a bug that shows up differently depending on how software is loaded.

In our case, an enormous flood of face-detection indications starts as soon as any camera related app is started.

It would likely help if someone else could check in their system if it is the same there.

Take a trace with LogCat as described in
http://developer.android.com/tools/debugging/debugging-projects.html

And check what reports are created very often while the battery is drained.

It is interesting that there are so many different reports on what helps. Different uninstallations and reinstallations. It seems that stirring around in memory causes the bug to be inactivated. Such things can depend on uninitialized variables or peeking in memory that does not belong to the module.

Since we get the face detection indication without requesting face detection, it seems to me that the face detection logic that should be done in background maximum once per image is spinning free as rapid as it can.

Is it the same cause in all these spontantaneous battery drain situations? Check the logs!    

Google plz fix this issue..uninstalling any app should not be a solution..

We do not yet really know if it is Google or device manufacturer causing this.

[Comment deleted]

As far as I can tell this started after I used an App called "ScanToPDF Free"  When I started the App, the camera crashed and wouldn't even open from the camera App.  I had to reboot the handset (Stock Nexus 5) to get the camera active again.

Opening ScanToPDF Free this time worked and a picture was taken.  However, the next day I noticed the fast battery drain and found this issue.  All I did was reboot the handset again and all has been fine.

My thought is that it could be any App that has access to the camera that could cause this fault.  It may be that the App crashes or just is not designed well and causes this drain.  I did not uninstall the App.  I have used it again since without fault and without recurrence of the "mm-qcamera-daemon" fault.

I am removing my Star on this topic, because I feel it IS to do with 3rd Party Apps and NOT Android Firmware.

Good luck to all in solving this issue for your devices.

Android 4.4.2, Nexus 5 - same issue: I did a factory reset, problem persisted. After that I rooted the phone, fixed permissions using ROM Manager. So far no more problems.

While I have some 3rd party apps using the camera I *think* the only camera accessing apps I'd used in the reboot cycle when I encountered this were Hangouts and Camera. No problems I could see with Hangouts, but the next day Camera refused to start and was just giving me "Can't connect to camera" error. That was the first hint something wasn't quite right, noticed the battery drain few hours later, it took less than three hours to drain the battery from full charge.

I have Nexus 5 since release.
Since last 2-3 days even my phone runs out of battery without much use - even in airplane mode...!

performing factory reset as I write this comment. Hope it solves the issue.

please call Google and report the issue if a reset doesnt help.

I am new to this site... but it seems clicking the "Star" next to the title "Issue 36949180: mm-qcamera-daemon cpu usage" registers a vote!

I hope these votes traslate in the prioritization of issues/bugs by google!

I'm a Nexus 5 owner. About one week ago I noticed that the camera app wasn't working at all ("Can't connect to camera" message). Since the last two days I noticed a heavy battery drain (the daemon takes about 60 %) and heat. I uninstalled snapchat, skype, tried to restart the phone, delete the camera shortcut, but nothing works, the daemon keeps operating. This IS a major issue, please fix it, my Nexus 5 doesn't even last a day.

It all has happened for the last week or so... First it was Foursquare that started draining battery like mad, with the app being active during a bunch of minutes despite I was not using it. Then the infamous camera daemon.

I haven't seen any problem after uninstalling Foursquare but I after reading your comments that doesn't look like the root cause at all :/

I dont think any app is responsible for this major drain.

I have done no major changes to my Nexus 5 and this issue came into existence from nowhere.

qccamera-daemon seems to be one of the issue and eats upto 35% of my usage but I don't feel it's the only one draining battery.

Same issue for me...  Started Thursday of last week, mm-qcamera-daemon drains the battery, phone gets very warm, camera doesn't work. A reboot seems to fix it until (I think) I take another picture. _very_ annoying obviously...

same here with my Nexus 5
facing this issue of "mm-qcamera-daemon" which is eating up the battery like its hungry for years.
@Google, #android#team please have a fix for this, resetting to factory default or uninstalling an app should not be a solution.

A lot of people believe it's snap chat that's causing the problem but I never installed snap chat and I still face this problem with the phone. In fact any app that uses camera seems to trigger this process and then it does not terminate causing fat battery drain for my phone.

Have a nexus 5 16gb, KitKat latest running on it

Isn't it possible to bump the priority on this? This is a major issue

Same Problem here. Tried different "fixes", none seems to be working.
Problem does not seem to be related to any app - just started "out of the blue".
Nexus 5, 16gb, Stock. Running 4.4.2 Kernel 3.4.0-gadb2201

I found this thread after having the same issue for the first time (Nexus 5 4.4.2 16GB).

I have a very strong hint about this (or just a HUGE coincidence): the battery drain from mm-qcamera-daemon started after I enabled the camera cloud backup from G+ photos app. I have never had this issue before doing this, so it should be the culprit.

Nexus 5 16 gb, 4.4.2 rooted

Happened to me last night (mm-qcamera-daemon the culprit), drained about 20-30% of my battery. Started while I accidentally clicked on the flash icon and then could not disable flash (have power toggles in the dropdown menu). Went into the camera app to try to disable flash and the camera crashed (same as post #103 and then a crash, message stays on the screen for a split second). Rebooted the device and the flash was still a bit unresponsive (didnt toggle on/off like it normally does, but with a lot more lag). The camera worked fine. In the period of about 20-30 mins 20% of the battery was gone. Funny enough the problem stopped abruptly as I switched my phone to airplane mode and went to bed. Phone works fine today.

Also I should mention that I do have photo upload to google enabled ever since I got the phone (2 months), but this is the first time it happened and the first time i saw mm-qcamera in the battery usage.

This issue started for me a few days ago on my Samsung Galaxy Note 3. I have instagram, snapchat, as well as lots of other camera styled apps. Never had an issue until the past week. Currently it is chewing up 40% of my battery. Tried uninstalling snapchat, barcode scanner, instagram, path, facebook, vine etc. rebooted, still there. This really shouldn't be an issue going on 5 months without a resolution. Are google even looking into this?

I am facing same problem with my nexus 5 KitKat 4.4.2...when I rebooted the mobile it was gone when I started using cam it started again...I have not installed any new apps recently..

Discovered this issue today, drain 60% of battery in a couple of hours, with no apparent trigger.  It seems to be a major issue.
Note 3 Orange jelly bean 4.3. Never happened on Note 1,Jelly Bean up to 4.2

This just started happening to me. My camera started acting funny today. It had a black screen, then my phone started to get hot and the battery drained in about 2 hours from a full charge. I have a Galaxy Note 3, Android Version 4.3. I have had no issues before today. I dont have Snapchat. I do have Skype, Facebook, and Dropbox.

Same here with Nexus 5 KitKat 4.4.2.

Does anyone have a fix? This is terrible!

same problem. To those saying it is caused by goggles/snapchat/other camera apps  - an app *should not* be able to cause this issue - android should force the release of the camera.

Same here with Nexus 5 KitKat 4.4.2, appears to have just started of the past week. I went to take a picture via 'Voxer' on Saturday and saw the 'cannot connect to camera' error message and had to reboot to get it working again. Since then, it keeps re-ocurring. Wow, it goes through the battery like nothing I've ever seen. I had the camera app button on my homescreen so have now removed this in the hope the problem goes away.

Same issue startet yesterday on my Nexus 5 out of nowhere - no new installed apps or something - just the mm-qcamera-daemon that is draining my battery.

What the hell is this ...  ?!

Nothing to install. Did a hard reset. To no avail. The problem mm-qcamera-daemon persisted.

Likewise I discovered this bug when I went to use the camera and it wouldn't open, soon after that my phone died as it ran out of battery, the culprit appeared to be this camera daemon.  Now it seems to happen sporadically.
I've not got snapchat or instagram, in this case the only apps I've actively used before it happens are Facebook, google+, googleNow and cameraFX.  I've used FB, G+ and Google now without it happening so I'm guessing it's probably whenever something opens the camera.  Current solution is to reboot daily and when I use the camera!

Nexus 5
Android 4.4.2
Baseband version M8974A-1.0.35.0.23
Kernel version 3.4.0-gadb2201 android-build@vpbs1.mtv.corp.google #1 wed Nov 20 13:42:53 PST 2013
Build Number KOT49H

I don't have SnapChat or InstaGram install - never have, and I also have this problem.

I'm pretty sure I've had this problem for a while but didn't notice till now.

I was really annoyed by slow recharge, and when the phone started getting really hot with no apps started I looked at battery usage and found mm-qcamera-daemon using 34% of all CPU time.

I've had my N5 for months and this problem started a few weeks ago - maybe several weeks ago.

Same Problem on my Nexus 5.
This seems to happen since ~ 2Days.

To make matters worse. Rebooting my phone does not make the problem go away!

Yes, it is quite evident now that
1. it appears from various camera-related apps.
2. And it shows up as the title says in extra CPU usage by the mm-qcamera-daemon.
3. Some have succeeded to get rid of the problem by various reshuffling of apps, system components or SD-card contents.
4. Nexus and some Samsung and one Motorola have appeared in the reports.
5. On NOTE 2014 we have seen that it is Face Detection looping wildly in mm-qcamera-daemon, but no one have reported what activities get logged in any other device.
I have succeeded to report to Samsung today but with no promise for rapid action.

In #50 a range of actions were reported, that together got rid of the problem.
It would be valuable if someone could test one of these actions at a time. I would suggest just removing and putting back mm-qcamera-daemon as the first one to try.

#84 describes my experience exactly.
Always have ended my days of light use with 65-80% battery remaining. Never installed snapchat or yahoo or instagram, never used face unlock, wasn't even using my camera this weekend, but all of a sudden yesterday the battery hit 14% by dinnertime! Restarting hasn't worked; today it's draining quickly too. My Nexus 5 is nearly ruined, until Google fixes this.

It started happening on my stock Nexus 5 (32 gb) as well since last week. No new installation just few updates. In some forum it was mentioned that Amazon app update was the reason. I uninstalled the app, still I have the issue. Please fix it asap

Same issue for me, and I don't use Snapchat, Yahoo or Instagram. It's been like that since more or less a week. In my case, as some reported, I had also the issue of the camera not working properly at some point (and for no apparent reason). I restarted the phone and the camera was there, but since, I have been dealing with this battery issue.

I have been trying to identify which app could be causing the trouble, so far unsuccessfully. I installed and app (os Monitor) which helped me to identify at what point the service associated with this (QcrilMsgTunnelService) started. It might be just coincidence, but at some point it told me that the service had been up for 8 hrs. 23 min. and XX secs, and that was exactly the amount of time Whatsapp have been running according to the same OS monitor, so it might be Whatsapp (I haven't installed it yet, I'll wait until the service "hangs around" again and then will double check if whatsapp and/or any other app started running at the same time the service did).

But even if I identify the responsible app and get rid of it, I'd like this issue "radically" solved, because otherwise it will be just a matter of time before another app activates it.

I believe we need to get this to Google. Posting here and adding stars to this post, is that the way to go? Thanks in advance for your reply.

I strace it when qq-camera-daemon eating power, "select" is looping because one pipe is broken. The pipe's fd is a fixed number 17.
A workroud way is to monitor qq-camera-daemon, when it is connected and pipe 17 disapear, just killed it. It will be restart automatically.

Who can fix this bug?

Same issue with stock Nexus 5, 4.4.2. Did not altered my app set in any way. I use the phone for a month now, never had such an issue before ~5 days ago. Never used snapchat - issue may manifest itself after any session with camera, most commonly through WhatsApp.
I suspect some recent update to Play Services or similar system-level silently-updating app does not behave well with Qualcomm camera driver.

Occurs on Nexus 5, 4.4.2, after the camera weird behavior several days ago (stuck on black screen on launching the camera app)

facing this issue in Nexus5 , stock KitKat. daemon-shaemon , my ass.
Enabling 'Dont keep Activities" in Developer Options won't fix this?

I am trying that and will report if I have a Eureka moment

Plus one. Stock N5,no snapchat. Started happening a few days back. Possibly started with a Google Play Services update or something similar beyond my control. Reboot fixes temporarily. This is a serious bug affecting a lot of people.

Happened to me as well..
Nexus 5, 4.2.2 32 GB

I didn't used neither camera nor any other application. When open the battery stat was surprised to see that battery drain was caused by camera-daemon. Was not able to launch camera post that. Reboot fixed the issue though..

Same problem here.

Nexus 5, 4.4.2 32 GB Version

Since yesterday (24th Feb. 14) in the evening my phone starts extremely draining the battery. Today after 3 hrs with battery it has only 50% of power left.

No camera usage, no snapchat. Came from nowhere.

Any fix for the problem ?
I am having this issue since a week ,each time i have to restart the device .

Same here with Nexus 5 KitKat 4.4.2.

Nexus 5, 4.4.2 32GB.
Same problem about a week.  
I've uninstalled goggles, but I'm not see any difference.

Hi!, I am another owner of a Nexus 5... the same problem... 3 times this week... please google solve this!!!

This happened twice to me now. Nexus 5 stock with no photo back-up turned on (G+, dropbox) and no custom camera app. Restarting the device seems to fix the issue, but not for good. Clearly it is related to the standard camera app, as I have got the "Can't connect to the camera" error message prior this issue. I think, restoring the phone is not a viable solution!

Same for me.

Nexus 5, 4.4.2 32GB.

Yesterday 50%, today 33%.

I took some pictures 2 days ago.

Joining the club..

Happened to me yesterday for first time...

Same problem with my wife's Nexus 5. I guess there is no solution. I can't believe this is a small priority still, it's a huge problem. Battery life is a number one priority for 99% of the smartphone community. Is there a proper way to report the problem to Google?

No luck with restarting the phone. Couldn't connect to the camera randomly. Seems like a recent matter. I spent two weeks road tripping across the states, using the phone as my primary camera most of the trip with no issues at all. It's as of recent that the battery's been draining fast. Unplugged this morning around 6:40, it's 8:40 now and I'm down to 59% already. Struggles to charge overnight.

Rebooting hasn't done anything for me.

mm-qcamera-daemon has been running between 43-51% on my phone.

Stock Nexus 5 32GB, Kitkat 4.4.2.

After keeping up to date with this regarding mm-qcamera-daemon, somehow today that process is no longer in the battery stats but I am still having issues with camera not opening. Says it 'cannot connect to camera' so the issue is still there. Only way to get camera working is to restart the phone. This bug seriously needs to be looked at.

Same problem with my Nexus 5 since a couple of days ago, I can't find a solution anywhere, I've tried tweeting to Android and Google hoping someone gets the message. Is there any oficial statement from Google? 5hr battery life all of the sudden is not what I sign in for!

Same for me, started yesterday.

Nexus 5, 4.4.2 16GB.

You should really change the priority.

This really needs to get fixed...

I've been using the Nexus 5 phone fine since November but two days ago I started experiencing huge battery drains. Today I installed Battery Monitor Widget and saw that mm-qcamera-daemon is using up 49% of the processor. Powering off and on does not solve the issue even temporarily. Removing any camera related apps (Lomo in my case) also made no difference.
The Apps mentioned by others like Snapchat and yahoo messengar are not installed.  I even deleted all non-essential apps but nothing changes. I haven't tried factory reset yet but want to leave this as the final option.

Really hope google is looking into this and announces something soon.

Same here. Nexus 5 32GB, 4.4.2. Noticed it yesterday and today.

Same here. Nexus 5 32GB, 4.4.2. Noticed it yesterday and today.

Same here. Note 3. Batt would last for full 12+ hr day for the past 3 months; starting about 3 days ago, I'm at 30% after about 4 hours of moderate use (but nothing more than usual). mm-qcamera daemon is taking up about 40%.

EXACT SAME PROBLEM!!!
Nexus 5, 4.4.2 32 GB Version
Started happening yesterday.
Right now after 3hrs 8mins on battery, down to 60% from 100% with near to no usage!  mm-qcamera-daemon at 45% battery usage, the next one is Mobile standby with 14%...

Totally unacceptable, someone get on a high profile website and report this as it's ridiculous that there is not even a 'Got it, working on it' from anyone on this problem.

+1 here, only noticed this today, only could solve it by opening the camera app, getting the error, then reebot, also the proccess appeared from nowhere, as on the latest charging cycle i've never used the camera lol.

Discovered the same issue on my Nexus 5 32G (821) today, mm-qcamera-daemon eating 50% of battery capacity.

Same for me,since a week on my stock n5: no yahoo no snapchat. Don't think it is caused by a particular app because this process can appear during the night whereas i'am slepping and not using the phone...

Now or never google...

I'm having a similar issue. It started about a week, maybe two weeks ago, at first just the "Cannot connect to camera" error, and I noticed that mm-qcamera-daemon has been eating my battery. Normally the screen is the largest battery drain, but now this one process has at least doubled that. I thought Instagram might have been the culprit but I have uninstalled that with no change.

Sprint Nexus 5, Android 4.4.2.

One more victim every half hour

Note 3, same issue that everyone is reporting.  Just happened to me today.  Come on Google!

[Comment deleted]

It happened to me because of "Clean Master" app shortcut, to put search light on. I had to reset my phone initially to get rid of this issue and then by mistake I touched the searchlight to on in the status bar which triggered mm-qcamera-daemon and thus started draining my battery. I am on Nexus 5.
Will report to Clean Master as well. But i don't think it's an application specific issue. It has more to do with some underlying process which is running in a loop draining the battery.

this effects me as well, very annoying to not feel as though you can trust it.

note 3. no root.. same problem:(

This is happening to me on a Sprint/Ting Nexus 5. Phone gets hot and completely drains within 5 hours on standby, 2-3 hours if using it.

This is making my phone borderline unusable. I am seeing the mm-qcamera-daemon at over 50% battery usage, and also getting "Cannot connect to camera" errors when trying to run the camera app.

This is a new phone, and if this isn't fixed I'm going to have to return it. I would much rather see this patched, since I like the phone otherwise.

2 Days back suddenly my battery gets drain within 7 to 8Hrs in which mm-qcamera-daemon is the guy who eats most of it. And after seeing one of the Post I check my camera, it was not working. I tried most of the hits above, but nothing worked.
After clearing all app cache, temp files and restarting 6 times, now camera is working.
I let full batter drain and charging on shutdown mode.
Hoping it should work this time.
Will keep posting how it goes.
Fingers crossed !!!

Nexus 5 with Android 4.4.2 here. I'm using ART instead of Dalvik.

Hangouts is my SMS app. I regularly use Pocket Casts, Play Music, YouTube, Timely, Chrome, Google Maps, Tumbler, Gmail, Twitter, Facebook, Facebook Messenger, Google Plus, Google Drive, Google Keep, GitHub, DashClock Widget, Tasks, SKype, Firefox, Google Authenticator, Play Books, Dungeon Keeper, and Ingress. I have full-device encryption enabled with a PIN prompt.

It was months ago that I was updated to Android 4.4.2, so I don't believe that update caused this issue by itself. I've only had this issue for the last week or so.

I do know that Google Play Services updates separately and secretly, so it's currently my number 1 suspect. I'm on version 4.2.23 (1035512-038) right now.

I don't know what else to mention. This bug is now happening to me on a daily basis and I have no idea what triggers it.

Love my Nexus5. Hate this bug. Please fix it.

Same here, first saw it today on my Nexus 5.  

I have had this issue as well. Had to uninstall Most of can apps.

I'm having same issue...don't use snap chat, but did update sky drive to one drive and opt to allow automatic uploading. Just turned that off and will see if anything changes.

Same as most people.. Have starred this post

This just DOESN'T look like an app specific issue. Google pls fix this asap- its gonna kill the N5.

Same here. Yesterday I saw this ... first time. Until now, this was not a problem on my Nexus 5 from November.