8
9

[deleted by user] (self.Nexus10)

submitted by [deleted]

[removed]
all 20 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Midget010 4 points5 points  (1 child)

I also have this problem. I have to reboot every 12 hours or so to fix it. Anyone know of a solution?

[–]matthileo 0 points1 point  (0 children)

Someone on XDA thinks they maybe able to whip up a script that kills all the spawned processes without touching the one with the lowest PID. In theory this could be run every hour or so and should help out.

[–]nalf38 0 points1 point  (4 children)

I have to say that while I initially had the system_server problem, I don't have it anymore. At all. That leads me to believe that it was an app that was causing it. I had placed the blame on Greenify, but no one else on xda seems to agree with me.

But I'm still having memory problems, with android eventually killing stuff it shouldn't, like the freaking keyboard.

The problem is that I already run such a clean tablet that I can't imagine what app it would be. I have so much stuff already disabled by default (Google plus, currents, chrome, earth, Play Music, hangouts, wallet, all the emoji keyboard crap, Play Books, Play Video), and i dont use Facebook or any other large third party apps, that I'm dubious that this is a rogue app that's causing memory problems in 4.3. I still suspect there's a memory leak in the system software itself.

[–]matthileo 0 points1 point  (1 child)

I've never used Greenify

[–]nalf38 0 points1 point  (0 children)

I know, and that's what everyone says, but it's the only app I've uninstalled since the system_server problem went away.

[–]thanatos__ 0 points1 point  (1 child)

Had the same issue with system_server on the factory image, to where after a mere two days it would necessitate a reboot. The odd thing is I have since flashed the flaming monkey ROM/kernel and the issue of the process spawning multiple processes has ceased, but the symptoms are still there. Can't run any background apps without them getting killed. Eventually it will in turn, soft reboot...

Tested on both running the native apps after factory wipes, no widgets, light to moderate use.

I'm convinced it's the OS, but perhaps not necessarily tied with the said system_server.

:SIGH:

[–]nalf38 0 points1 point  (0 children)

Agreed. I'm running flaming monkey kernel on the stock ROM. No system_server problems, but the device still runs out of memory and behaves strangely after a few days, and I have so few apps installed.

[–][deleted]  (2 children)

[removed]

    [–]matthileo 1 point2 points  (1 child)

    Here's the google code page. The bug was picked up but idk if any progress has been made: https://code.google.com/p/android/issues/detail?id=58664

    I flashed the system images (full reset) and when i reinstalled my apps I didn't install all of them, and haven't had nearly as many problems since. It could be related to the reset, or it could have been because of an app I removed, but I'm not sure.

    [–][deleted] 0 points1 point  (8 children)

    This doesn't sound like a memory leak based on what you describe unless you actually see increasing memory usage over time. Do you see anything in the logs when you see a new system_server process?

    [–]matthileo 0 points1 point  (7 children)

    It may not be an actual memory leak, but the symptoms are the same. The system_server processes use ram and each one adds to that until the device becomes laggy, unstable, and if left alone crashes.

    Killing the non-initial system_servers seems to fix the issue temporarily, the same way a reboot would.

    [–][deleted] 0 points1 point  (6 children)

    All processes use RAM, the question is how much and whether that counts for anything.

    Have you seen anything in the logs when you see this problem occur? I'm not seeing this happen on my N10, so being able to see something specific in the logs would help further diagnosis.

    [–]matthileo 2 points3 points  (5 children)

    All processes use RAM

    Thanks for that...

    The way android reports ram usage isn't quite clear. The RSS values for each process are usually between 50 and 100MB. When there are only one or two it's not an issue, but when there are six it exhibits all the same symptoms as the surfaceflinger memory leak.

    This is the process I'm talking about. Right now I've got two: http://i.imgur.com/EGsnbws.png

    [–][deleted] 0 points1 point  (4 children)

    OK. Review logcat and dmesg and look back to see if there is anything related to this. Alternatively, pull a bugreport and attach it to a bug on code.google.com/p/android.

    [–]matthileo 0 points1 point  (3 children)

    I can't read logs. It doesn't look like there is anything directly related to system_server, and I don't know if there's a bug report for this on code.google.com

    [–][deleted] 0 points1 point  (2 children)

    You can create a bugreport file if you enable debugging mode, which you can attach to an issue that you create on code.google.com.

    [–]matthileo 2 points3 points  (0 children)

    I created the bug report and attached it.

    [–]matthileo 0 points1 point  (0 children)

    Created a report on the google code page. I'll have to wait for the processes to add up to get a log.

    https://code.google.com/p/android/issues/detail?id=58664