Ok, waiting for your feedback.
Support Forum
Search found 2328 matches
Same thing with alternating between "reschedule" and "rescheduleForward" - initial "rescheduleForward" allocates some extra memory (same as initial "reschedule"), further "rescheduleForward" stays at the same memory usage. See the video in the github...
Right, this is the order of capturing the onBarcodeScanned method. The only proper way would be to load your application code first (w/o launching it), install the override in the class'es prototype, then launch the app (so that the app captures the override). But may be you can test some other side...
Hello, You mentioned the SmartMobile.util.Barcode.onBarcodeScanned('T|123123123'); works, which means Siesta correctly intercepts the onBarcodeScanned method in the MyApp.util.Barcode object. As regarding Ext.fireEvent('barcodeScanned', 'T|123123123'); - this is something specific to your applicatio...
What happens during "reschedule" operation is that during the initial "reschedule" extra memory is allocated, however further "reschedules" do not do that (all extra allocated memory is released). Please see the video in the github ticket. To investigate what is allocat...
I wasn't able to reproduce the memory leak - please see the video posted in the github ticket. Any additional information about how to reproduce it? > also the question for me is why there is such an enormous increase of the data compared to the raw data This is because of reactivity. All dependenci...
Can you switch the gantt bundle in the test to non-minified version please? Also, the leak does not seem to be obvious. For example it starts with 39.4MB, then after series of moves it becomes 41.1MB and memory snapshots are pretty much identical. Some increase in the "compiled code" and &...
Ok, will checking there. In our examples, the move task operation does not seem to produce any leaks (repeatedly moving a chain of 500 tasks)
@pincherhgz Hello. Sorry for delay. Regarding this issue - I have fixed the leak in case of dependency add/remove, now checking the "move task" case. The test app does not seem to load, so I'll be trying to reproduce it in our examples. I assume the move is performed with a regular drag an...
Thanks for the update, please keep us posted.