Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while parsing trace #4

Open
fat-fellow opened this issue Jul 23, 2018 · 4 comments
Open

Error while parsing trace #4

fat-fellow opened this issue Jul 23, 2018 · 4 comments

Comments

@fat-fellow
Copy link

fat-fellow commented Jul 23, 2018

Error processing A45AE0568CD949FC1C8DB04987A79E18

Please open an issue if this is not what you had hoped for.
Guru meditation:
{{case_clause,[<<>>]},
 [{aflame_trace_parser,parse_method_line,1,
                       [{file,"/src/_build/prod/lib/aflame/src/aflame_trace_parser.erl"},
                        {line,401}]},
  {aflame_trace_parser,'-parse_methods/2-fun-2-',2,
                       [{file,"/src/_build/prod/lib/aflame/src/aflame_trace_parser.erl"},
                        {line,390}]},
  {lists,map,2,[{file,"lists.erl"},{line,1239}]},
  {aflame_trace_parser,parse_methods,2,
                       [{file,"/src/_build/prod/lib/aflame/src/aflame_trace_parser.erl"},
                        {line,388}]},
  {aflame_trace_parser,parse,1,
                       [{file,"/src/_build/prod/lib/aflame/src/aflame_trace_parser.erl"},
                        {line,276}]},
  {aflame_trace_parser,handle_cast,2,
                       [{file,"/src/_build/prod/lib/aflame/src/aflame_trace_parser.erl"},
                        {line,98}]},
  {gen_server,try_dispatch,4,[{file,"gen_server.erl"},{line,637}]},
  {gen_server,handle_msg,6,[{file,"gen_server.erl"},{line,711}]}]}

AS 3.2 Beta 4

@rschlaikjer
Copy link
Owner

Hmm, interesting - this file doesn't appear to have the format you'd expect based on this trace code for ART I've been using for reference.
A couple questions so I can better look into this:
Did you generate this dump using android studio? Or using the Debug.startMethodTracing call?
What device did you use? What android version?
Thanks.

@fat-fellow
Copy link
Author

Sure.

  1. Yes, just using Android Studio (sampled option). Profiler was attached from start.
  2. Samsung Galaxy s7
  3. Android 8.0.0 (firmware G930FXXU2ERD6) (I was able to attach the profiler to an app from start only since this version).

@rschlaikjer
Copy link
Owner

Hmm, interesting. I will try to replicate using Android studio when I have a moment. In the meantime, would you be able to take another trace, using the Debug.startMethodTracingSampling method call, and check if that works? It could be that android studio is doing something unexpected here. If that also doesn't work, this might be Samsung specific behaviour.

@fat-fellow
Copy link
Author

I have tried and in this case everything works just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants