android - cordova 3.0 FileWriter THREAD WARNING: exec() call to File.write blocked the main thread...should use CordovaInterface.getThreadPool() -


i'm using filewriter , works fine except these messages in logcat when write largish files of various sizes upto 3mb.

i had @ fileutils.java source , write function doesn't use getthreadpool() interface (the reader does).

as test thought i'd adapt filewriter use runnable interface , able code compile , execute - unfortunately logcat messages still show up...

the blocking times between 25ms , 1200ms far. haven't run serious comparison tests determine if change makes real difference - looking absence of logcat messages.

would these changes below make real difference?

are these message should worry about?

my java pretty basic - here changes made - following reader implementation.

else if (action.equals("write")) {     this.write(args.getstring(0), args.getstring(1), args.getint(2), args.getboolean(3), callbackcontext); } /* original code else if (action.equals("write")) {     long filesize = this.write(args.getstring(0), args.getstring(1), args.getint(2), args.getboolean(3));     callbackcontext.sendpluginresult(new pluginresult(pluginresult.status.ok, filesize));

} */

and in write function below...

public void write(string filename, final string data, final int offset, final boolean isbinary, final callbackcontext callbackcontext) throws filenotfoundexception, ioexception, nomodificationallowedexception { if (filename.startswith("content://")) {     throw new nomodificationallowedexception("couldn't write file given content uri"); }  final string fname = filehelper.getrealpath(filename, cordova);  this.cordova.getthreadpool().execute(new runnable() {     public void run() {         log.d(log_tag, "starting write");         try {             boolean append = false;             byte[] rawdata;             if (isbinary) {                 rawdata = base64.decode(data, base64.default);             } else {                 rawdata = data.getbytes();             }             bytearrayinputstream in = new bytearrayinputstream(rawdata);             fileoutputstream out = new fileoutputstream(fname, append);             byte buff[] = new byte[rawdata.length];             in.read(buff, 0, buff.length);             out.write(buff, 0, rawdata.length);             out.flush();             out.close();             log.d(log_tag, "ending write");             callbackcontext.sendpluginresult(new pluginresult(pluginresult.status.ok, rawdata.length));         } catch (ioexception e) {             log.d(log_tag, e.getlocalizedmessage());             callbackcontext.sendpluginresult(new pluginresult(pluginresult.status.io_exception, not_readable_err));         }     } });

}

yes, these messages important , should use background thread complicated tasks, such file writing. reason of problem these tasks blocking cordova , experience example ui lags.

if next actions dependent on task being completed, recommend using callback method.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more