I wonder if there's some data change somewhere that causes an issue?
I guess the curious part would be if a full flash of the v5 cause the same
issue to occur?
Seems odd that would happen though.

On Thu, Jan 21, 2016 at 12:00 PM, Mihai Barbat <[email protected]> wrote:

> I understand. I didn't do anything out of the ordinary on the Flame except
> sideloading the V5 like Naoki instructed last week.
>
> On Thu, Jan 21, 2016 at 8:57 PM, Alexandre Lissy <[email protected]>
> wrote:
>
>> Le 21/01/2016 20:55, Fabrice Desré a écrit :
>> > thanks! So twitter makes the parent process memory usage go through the
>> > roof. Either we leak or we have something seriously bad.
>> > Any chance to get full logs before twitter dies? (the ones you get from
>> > shaking)
>>
>> FYI I tried to reproduce this multiple times on several other devices
>> including Nexus 5 L, Z3c L and Z3c KK. None exposed that behavior. Even
>> on profiles I heavily made use of Twitter in the past.
>>
>> >
>> >
>> > On 01/21/2016 11:42 AM, Mihai Barbat wrote:
>> >> Here you go!
>> >>
>> >> On Thu, Jan 21, 2016 at 8:30 PM, Fabrice Desré <[email protected]
>> >> <mailto:[email protected]>> wrote:
>> >>
>> >>     Thanks Mihai,
>> >>
>> >>     Unfortunately we don't have the most useful info from b2g-info
>> because
>> >>     it's not running as root. Can you try to first to run |adb root| ?
>> >>
>> >>     On 01/21/2016 11:18 AM, Mihai Barbat wrote:
>> >>     > Hi Fabrice
>> >>     >
>> >>     > Here is the dump. 1 second before Twitter is started and then
>> every
>> >>     > second until the homescreen crashes and restarts. I also
>> attached the logs.
>> >>     >
>> >>     > I hope it will help. If you need anything else please tell me
>> and I'll
>> >>     > gladly help.
>> >>     >
>> >>     > Mihai
>> >>     >
>> >>     > On Thu, Jan 21, 2016 at 6:50 PM, Fabrice Desré <
>> [email protected] <mailto:[email protected]>
>> >>     > <mailto:[email protected] <mailto:[email protected]>>>
>> wrote:
>> >>     >
>> >>     >     We're getting a major OOM. Unfortunately the memory report
>> doesn't
>> >>     >     include Twitter so we can't say how bad twitter itself is,
>> but the
>> >>     >     homescreen is eating > 50MB which is high.
>> >>     >
>> >>     >     If you can run |adb shell b2g-info| while you launch twitter
>> (eg every
>> >>     >     second) that would help.
>> >>     >
>> >>     >             Fabrice
>> >>     >
>> >>     >     On 01/21/2016 09:36 AM, Naoki Hirata wrote:
>> >>     >     > Yikes.  [  241.564712] Killing 'b2g' (229), adj 0,
>> >>     >     > B2G basically got killed and restarted, which explains the
>> black out and
>> >>     >     > the SIM coming back.
>> >>     >     >
>> >>     >     > There's definitely a bug going on here; we need to narrow
>> down these
>> >>     >     > steps so that we have constant reproducible actionable
>> items.
>> >>     >     >
>> >>     >     > Currently just saying 2 days twitter, when there's a lot
>> more stuff
>> >>     >     > going on is going to be hard to reproduce for anyone
>> including the devs
>> >>     >     > working on the issue.
>> >>     >     >
>> >>     >     >
>> >>     >     >
>> >>     >     > On Thu, Jan 21, 2016 at 9:27 AM, Naoki Hirata <
>> [email protected] <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>
>> >>     >     > <mailto:[email protected] <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>>> wrote:
>> >>     >     >
>> >>     >     >     If you delete the app then the problem seems to go
>> away; it sounds
>> >>     >     >     more or less like a caching issue and/or possible
>> memory leak
>> >>     >     >     somewhere ( maybe even in the app).
>> >>     >     >
>> >>     >     >     Seems like you're also getting data through your sim
>> instead of
>> >>     >     >     wifi; otherwise it shouldn't ask for your sim upon
>> returning from
>> >>     >     >     the screen.  Screen going black sounds like the screen
>> timeout hit.
>> >>     >     >     We should look through the logs to see if that was the
>> case.
>> >>     >     >
>> >>     >     >     Regardless, we probably need to run a test with
>> twitter scrolling
>> >>     >     >     through several days to see if we can reproduce the
>> issue with
>> >>     >     >     several days up time.
>> >>     >     >
>> >>     >     >     On Thu, Jan 21, 2016 at 9:19 AM, Mihai Barbat <
>> [email protected] <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>
>> >>     >     >     <mailto:[email protected] <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>>> wrote:
>> >>     >     >
>> >>     >     >         Hi Kevin
>> >>     >     >
>> >>     >     >         The issue gets worse as you keep using Twitter and
>> it was fixed
>> >>     >     >         when I deleted the app and reinstalled it again.
>> But in 2 days
>> >>     >     >         of using it normally it came back at the point
>> where when I
>> >>     >     >         start it the whole screen gets black for more than
>> 1 minute than
>> >>     >     >         somehow the screen recovers and it's asking me to
>> input my sim
>> >>     >     >         code again! then all the icons are repainted and
>> the homescreen
>> >>     >     >         appears.
>> >>     >     >
>> >>     >     >         I updated the bug with new logs
>> >>     >     >
>> >>     >     >         On Wed, Jan 20, 2016 at 10:21 PM, Kevin Tucker
>> >>     >     >         <[email protected] <mailto:
>> [email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>
>> >>     >     <mailto:[email protected] <mailto:
>> [email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>>>
>> wrote:
>> >>     >     >
>> >>     >     >             Hello Mihai,
>> >>     >     >
>> >>     >     >             We are unable to reproduce this issue so far
>> but we are
>> >>     >     >             investigating this further to be sure.
>> >>     >     >
>> >>     >     >             Thanks!
>> >>     >     >
>> >>     >     >             On Tue, Jan 19, 2016 at 9:02 AM, Mihai Barbat
>> >>     >     >             <[email protected] <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>
>> >>     >     <mailto:[email protected] <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:[email protected]>>>> wrote:
>> >>     >     >
>> >>     >     >                 Hi all
>> >>     >     >
>> >>     >     >                 Can you please try to run the Twitter app
>> or access
>> >>     >     >                 twitter.com <http://twitter.com> <
>> http://twitter.com>
>> >>     >     <http://twitter.com>? I get a completely
>> >>     >     >                 black screen and I think only the Flames
>> with V5 are
>> >>     >     >                 affected!
>> >>     >     >
>> >>     >     >                 Btw, I am running OTA 20160119030400
>> >>     >     >
>> >>     >     >                 Here is the bug
>> >>     >     >
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1240347
>> >>     >     >
>> >>     >     >                 Regards,
>> >>     >     >                 Mihai
>> >>     >     >
>> >>     >     >
>>  _______________________________________________
>> >>     >     >                 dev-fxos mailing list
>> >>     >     >                 [email protected] <mailto:
>> [email protected]>
>> >>     <mailto:[email protected] <mailto:
>> [email protected]>>
>> >>     >     >                 <mailto:[email protected]
>> >>     <mailto:[email protected]>
>> >>     >     <mailto:[email protected] <mailto:
>> [email protected]>>>
>> >>     >     >
>> https://lists.mozilla.org/listinfo/dev-fxos
>> >>     >     >
>> >>     >     >
>> >>     >     >
>> >>     >     >
>> >>     >     >         _______________________________________________
>> >>     >     >         dev-fxos mailing list
>> >>     >     >         [email protected] <mailto:
>> [email protected]>
>> >>     >     <mailto:[email protected] <mailto:
>> [email protected]>>
>> >>     >     <mailto:[email protected]
>> >>     <mailto:[email protected]>
>> >>     <mailto:[email protected] <mailto:
>> [email protected]>>>
>> >>     >     >         https://lists.mozilla.org/listinfo/dev-fxos
>> >>     >     >
>> >>     >     >
>> >>     >     >
>> >>     >     >
>> >>     >     >
>> >>     >     > _______________________________________________
>> >>     >     > dev-fxos mailing list
>> >>     >     > [email protected] <mailto:
>> [email protected]>
>> >>     <mailto:[email protected] <mailto:
>> [email protected]>>
>> >>     >     > https://lists.mozilla.org/listinfo/dev-fxos
>> >>     >     >
>> >>     >
>> >>     >
>> >>     >     --
>> >>     >     Fabrice Desré
>> >>     >     b2g team
>> >>     >     Mozilla Corporation
>> >>     >     _______________________________________________
>> >>     >     dev-fxos mailing list
>> >>     >     [email protected] <mailto:
>> [email protected]>
>> >>     <mailto:[email protected] <mailto:
>> [email protected]>>
>> >>     >     https://lists.mozilla.org/listinfo/dev-fxos
>> >>     >
>> >>     >
>> >>
>> >>
>> >>     --
>> >>     Fabrice Desré
>> >>     b2g team
>> >>     Mozilla Corporation
>> >>
>> >>
>> >
>> >
>>
>> _______________________________________________
>> dev-fxos mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-fxos
>>
>
>
> _______________________________________________
> dev-fxos mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-fxos
>
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to