[ 
https://issues.apache.org/jira/browse/WEEX-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566442#comment-16566442
 ] 

ASF GitHub Bot commented on WEEX-547:
-------------------------------------

weex-bot commented on issue #1389: [WEEX-547][jsfm] Remove module proxy cache 
of weex.requireModule
URL: https://github.com/apache/incubator-weex/pull/1389#issuecomment-409831492
 
 
   
   <!--
     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]


> Remove module proxy cache in each instance
> ------------------------------------------
>
>                 Key: WEEX-547
>                 URL: https://issues.apache.org/jira/browse/WEEX-547
>             Project: Weex
>          Issue Type: Bug
>          Components: JSFM
>            Reporter: Hanks Zhang
>            Assignee: Hanks Zhang
>            Priority: Major
>
> JS Framework has a cache strategy for module proxies which is good for 
> performance. But it also a potential reason for the memory leak.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to