[
https://issues.apache.org/jira/browse/WEEX-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610015#comment-16610015
]
ASF GitHub Bot commented on WEEX-518:
-------------------------------------
weex-bot commented on issue #1507: [WEEX-518][android] JVM garbage collection
took too long
URL: https://github.com/apache/incubator-weex/pull/1507#issuecomment-420121081
<!--
0 failure:
1 warning: No Changelog chan...
1 messages
-->
<table>
<thead>
<tr>
<th width="50"></th>
<th width="100%" data-danger-table="true">Warnings</th>
</tr>
</thead>
<tbody><tr>
<td>:warning:</td>
<td>No Changelog changes!</td>
</tr>
</tbody>
</table>
<table>
<thead>
<tr>
<th width="50"></th>
<th width="100%" data-danger-table="true">Messages</th>
</tr>
</thead>
<tbody><tr>
<td>:book:</td>
<td>danger test finished.</td>
</tr>
</tbody>
</table>
<p align="right">
Generated by :no_entry_sign: <a
href="http://github.com/danger/danger-js/";>dangerJS</a>
</p>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> JVM garbage collection took too long
> -------------------------------------
>
> Key: WEEX-518
> URL: https://issues.apache.org/jira/browse/WEEX-518
> Project: Weex
> Issue Type: Bug
> Components: Android
> Reporter: fudongrong
> Assignee: codefurture
> Priority: Major
> Attachments: 283F88A2-271E-4148-AEB2-8C6F8D3688D7.png,
> 900D11CE-85DB-4edc-926A-4AC6F124E772.png
>
>
> this crash is from android release apk.but i do not know whattime
> it will be happened,but it seems like crash from weex,this is crash explain
> from fabric:
> This is an Android system-level crash that happened because JVM
> garbage collection took too long. It was likely caused by an incorrect
> clean-up of native resources, or because garbage collection occurred while
> your app was backgrounded. Although this crash cannot be avoided, you can
> mitigate its effects. For more details, check out the first resource.
> the stack of crash please look at attachment,thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
