Android lost responding for about 50 seconds after first 1 minutes since launching

see Android Game is not responding after minute - Mobile - Epic Developer Community Forums for detail.

To reproduce this, you can just put a paper2d filpbook sprite in the level, and launching the game on android device. After about 60 seconds, the device will begin to lose responding for 50 seconds. It will resume responding after freezing over.

[link text][1]

72273-mytestbutton.zip (4.32 MB)

Hello Neckshot,

I was unable to replicate this on the . Could you please tell me what type of device you’re experiencing this on and please also provide the from the device. You can do so by going to: C:\android-sdk-windows\tools and opening up Monitor.bat and saving the once the game is running, during it’s freezing and afterwards.

Thank you!

Hi, engineer! Thank you for your reply, and happy new year 2016!
It is late for checking your answer for my vocation of new year!
I did the test according your advice, and here is the result:
Device: Lenovo A76000-F
Adroid ver: 4.4.2
Lost Responding Period: 14:14:00~14.14:57

It seems like processing dns resolve about internet address, I just guess

72651-log.txt (3.44 MB)

Neckshot,

I have tested a sample project with a paper2d flipbook. I added it into the project and allowed it to run. I could not replicate what you’re claiming on the Lenovo S939, which is the closest device that we have, that I could find.

The project that you provided me to test with was able to launch on a but it was unable to launch onto the Lenovo S939, no matter what I tried. The project would simply crash. But from my understanding, you’re not receiving a crash, the game freezes?

Looking forward to hearing back from you, thanks!

No, no crash happens. It just freezes for about 50 seconds, lost any responding at the same time, the game will resume after that and no freezeing happens again, just once.

See the lost responding period: 14:14:00~14:14:57 from my log, it looks like something happens: No log info “D/BufferQueue(133)” between this period.

finally, I figured out how to reproduce the bug:

1, enable and connect your wifi of your android device

2, block the internet access of your android device on the router.

3, the bug occoured.

I seems like one internal dns resolve request blocked the main thread.

Hey Neckshot,

Thank you for providing the exact reproduction steps. I have gotten this to reproduce on our Lenovo S939 but I could not get it to reproduce on an , or a Samsung Galaxy Note 2. With that being said, the bug has been reported as: UE-24954.

I will update this post as soon as I hear additional information, thanks!