全栈之力

内存泄露问题

3

打开demo页，播一个ws-flv直播，播大约1天，浏览器报out of memory。 可使用Chrome的F12工具录制，录制7分钟，可观察录制过程中，每秒钟都会产生一点点未释放的内存。 选中会发现，存在相当多的n引用，图中有672个n，随着时间一直增加   我已经把日志注释了，应该可排除是日志导致问题 我这边使用iframe复制了10份demo页同时播，崩溃速度更快。 ```html video Client v1 .player-iframe {width:450px;height:540px} ``` 

[功能需求] 节点拖拽

1

通过拖拽节点，改变节点在树结构中的位置

Wrong result while quering by $lt/lte/gte with a large numeric string property

1

my code: ```js let t; let alarms = []; for (let i = 0; i < 80000; i++) { let id = "74590869096" + (907836 + i); alarms.push({id, name: 'hello'...

Pretty slow while removing one-by-one

1

i have a real time system, i need to add/remove items one-by-one from the db, here's my example: ```js let t; let alarms = []; for (let i = 0;...

Wrong result while quering by $in with an index on a large numeric string property

1

my code: ```js let t; let alarms = []; for (let i = 0; i < 10000; i++) { alarms.push({id: "74590869096" + (907836 + i), name: 'hello' + i}); }...

I have tried to import ForerunnerDB in webworker, but i failed. in my worker.js: ``` importScripts('./node_modules/forerunnerdb/js/dist/fdb-core.min.js') ``` it doesn't work.

**Is your feature request related to a problem? Please describe.** 1. 希望通过一种方式来辨别view, viewed, hide, hidden这些事件是由用户主动点击viewerjs自身的控件触发的，还是编程式调用viewer实例的view()、hide()等函数触发的。 2. 当编程式调用viewer实例的view()函数触发view, viewed事件时，希望这些事件能与对应的view()方法共享同一个上下文对象。例如，调用view时我有一个上下文对象 {calledFrom:'component1'}，当收到view事件时，希望从事件中取回这次调用view函数时传入的这个对象{calledFrom:'component1'}，用来追溯与本次view事件对应的调用view函数时的系统状态之用。hide函数、hide事件、hidden事件也是同理。 **Describe the solution you'd like** 可行的建议方案： 1. 在view, viewed, hide, hidden事件的event对象中加入一个"triggeredBy"字段，...

成功运行frpc，但是回到桌面后，frpc就被暂停了。希望能保持frp实例后台运行。

希望frpc frps都支持多实例运行 一个实例不太够用

ngAA's Compatibility with ui-router v1.0+

1

ui-router v1.0.x is released. Currently, All state events, (i.e. $stateChange* and friends) are deprecated and disabled by default. [https://ui-router.github.io/guide/ng1/migrate-to-1_0](https://ui-router.github.io/guide/ng1/migrate-to-1_0) Do you have any idea on the ngaa's update for Compatibility...