Hey Chris
not a bad idea - I will give that a shot. I do see the gc endlessly
working during
and around the suspension time.
Thanks
On Sep 24, 12:29 am, Chris Stratton wrote:
> Garbage collecting might suspend your thread. But then so might
> trying to write to the log when the garbage collec
Garbage collecting might suspend your thread. But then so might
trying to write to the log when the garbage collector is also writing
to it.
If you want to investigate this, I'd try logging time stamps to a pre-
allocated buffer for a while, then dumping them out all at once or
doing some statist
He he - don't feel bad Jason - I would have said the same thing to
anyone
who said that to me as well ;) Well the truth is that it is around
12-14
threads running (I said 100 because I do know there are more
components
in this baseline that are threaded and have not been deployed yet) but
this
is
mm.. no. I only have 2 or 3 threads. Maybe that's the problem.
I always hate it when people say this.. but.. maybe you should
consider whether having 100+ threads is really appropriate for a
mobile device?
Actually even outside mobile devices, I have worked on some very large
scale, high-transa
Hey Jason,
it's running in the foreground - that's why this was a bit troubling.
Do you have a large number of threads running in your case (100+)?
Thanks
On Sep 22, 1:59 pm, Jason wrote:
> Is your app running in the foreground during all of this? I have
> threads running continuously without
Is your app running in the foreground during all of this? I have
threads running continuously without any issues.
If your app is NOT running in the foreground then it may well be
suspended by the platform. As a "general" rule the onPause method of
an Activity should also gracefully pause your th
6 matches
Mail list logo
