Closed GoogleCodeExporter closed 9 years ago
the android2cloud extension shouldn't be using up many system resources at all.
If you open the chrome task manager it sits below 6200k memory usage, and has
no network or cpu usage. The only time it really does anything is when you
click it, when it fetches the url to open. Besides that it does not use any
system resources.
Original comment by zyph...@gmail.com
on 7 Nov 2010 at 11:36
The extension sends an HTTP request every ten seconds. Hypothetically, it
shouldn't be a noticeable strain on your computer. It's possible, if you have a
slow net connection, that it could begin to be noticeable. What metrics are you
concerned about, specifically?
Original comment by foran.pa...@gmail.com
on 8 Nov 2010 at 1:27
@ zyphern, comment 1: I am not able to test it now because of the usual
"Service unavailable" message on my phone when trying to send a web page, but I
am almost certain that a2c launches links in the browser automatically (Linux,
Chrome beta channel)
@ foran, comment 2: In my case, the connection speed is usually no issue, and
one HTTP request every ten seconds does not sound very intimidating - not more
than Chrome's own sync function or my Xmarks extension, I would assume.
However, I think there are some (many?) users who - like me - prefer to keep
Chrome as lean as possible, and use Firefox and its add-ons for special
purposes. Contrary to Xmarks and the Chrome sync, a2c is not likely to be
something I need every day, but it is still desirable to have it in my default
browser.
Therefore, a pause option - or the option that the a2c chrome extension only
contacts the cloud in order to fetch links after the icon has been clicked -
would be preferable.
Original comment by mbartn...@gmail.com
on 8 Nov 2010 at 2:16
@mbartnaes Sorry for the really late response to this. I agree that a
minimalist version would be nice. Could you go ahead and open an Enhancement
request for it?
Original comment by foran.pa...@gmail.com
on 19 Nov 2010 at 9:53
The extension is currently using 57MB of memory for me in Google Chrome
10.0.648.134 on Ubutu 10.10 - FAR more than any other extension running.
Screenshot attached. I'm running '2Cloud' version 2.0.5. My browser has been
open for probably 12ish hours. I haven't opened any tabs using 2cloud at all
this browser session.
Original comment by flynsa...@gmail.com
on 16 Mar 2011 at 2:27
Attachments:
That definitely doesn't seem right. I'll look into it and see if there's
anything that could be causing a never-ending loop.
Could you post the console output from background.html?
Original comment by foran.pa...@gmail.com
on 16 Mar 2011 at 5:18
The same happens for me. Moreover, when the extensions consumes so much
resources it does not work. I.e. links sent to the browser do not open. Only
when the extension is killed and restarted using Chrome's task manager or when
the browser itself is restarted, the backlog of links sent is opened.
Original comment by UrK...@gmail.com
on 4 Apr 2011 at 4:36
Could you submit the log from the console?
http://links.2cloudproject.com/chromeconsole
Original comment by foran.pa...@gmail.com
on 5 Apr 2011 at 8:40
This issue has migrated to Github: https://github.com/2cloud/Chrome/issues/10
Original comment by foran.pa...@gmail.com
on 6 Aug 2011 at 9:57
Original issue reported on code.google.com by
mbartn...@gmail.com
on 7 Nov 2010 at 8:02