Spinning Wheel

[DEP/Dodo]

I have been experiencing the "spinning wheel" every time I open up Gmail via Chrome and only Chrome.  I checked in Help and searched within this group but found no explanation.  I am guessing that many of you have seen this as well.  Does anyone know why this occurs?  ~Dodo

[mollys57]

me too, it seems to load and load and load, the little wheel spinning
away. I have had secondary trouble with chrome too and may head over
to the chrome forum, frequently, it wont let me play games on pogo,
they just freeze or wont load and yet, internet explorer they load
right away..I hate E, so it makes me sad. will go there and inquire as
to fix.

On Sep 1, 12:02 am, "DEP/Dodo" <depfah...@gmail.com> wrote:
> *I have been experiencing the "spinning wheel" every time I open up Gmail

> via Chrome and only Chrome.  I checked in Help and searched within this
> group but found no explanation.  I am guessing that many of you have seen

> this as well.  Does anyone know why this occurs?  **~Dodo*

[bill hansen]

I just got Gmail running under Chrome today, using the offline app, and it opens up almost instartly. I like the interface.

 

Now I have to figure out how to get Calendar working offline, and whether I can work on Gmail offline from my cell phone. Anyone have any thoughts on that latter problem?

 

Bill Hansen

--
You received this message because you are subscribed to the Google Groups "Gmail-Users" group.
To post to this group, send email to gmail...@googlegroups.com.
To unsubscribe from this group, send email to gmail-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gmail-users?hl=en.

[John Blake]

I too get the constant load in gmail, but not always. It doesn't seem
to affect the page content or speed so I just ignore it. Not sure if
others are having content not loadin compltely, but my current page
seems complete with images etc.

> --
> You received this message because you are subscribed to the Google Groups
> "Gmail-Users" group.
> To post to this group, send email to gmail...@googlegroups.com.
> To unsubscribe from this group, send email to
> gmail-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/gmail-users?hl=en.
>
>

--
Sent from my mobile device

Cheers

John Blake

[Andy]

> I too get the constant load in gmail, but not always. It doesn't seem
> to affect the page content or speed so I just ignore it.

Ditto on all three.

When it happens (about 75% of the time), it often seems to keep doing
it for 20 seconds to a few minutes, then stops (finished loading or
something times out).

If I click on the "X", it stops spinning, and nothing else seems to be
affected that I can see.

Andy

[Marko Vukovic]

Hi D

My guess would be that it's because Gmail uses scripts that maintain a connection with the server, caching data and updating the interface as new email arrives.

On Thursday, September 1, 2011, DEP/Dodo wrote:

I have been experiencing the "spinning wheel" every time I open up Gmail via Chrome and only Chrome.  I checked in Help and searched within this group but found no explanation.  I am guessing that many of you have seen this as well.  Does anyone know why this occurs?  ~Dodo

Regards

--

Marko 

--
Marko

[DEP/Dodo]

I ignore it as well, but it is distracting.  ~Dodo

[DEP/Dodo]

I don't want to misunderstand, Andy.  What "X"?  The only one I can think of (without using Chrome at this moment) would cause exiting from the page.  ~Dodo

[DEP/Dodo]

I will try to be alert to see if this happens with all the computers at home on which I use Chrome.  ~Dodo

[Hilmy Hasanuddin]

The X icon represent "stop" loading any page at chrome.

---

From: "DEP/Dodo" <depf...@gmail.com>

Sender: gmail...@googlegroups.com

Date: Fri, 2 Sep 2011 11:39:37 -0700

To: <gmail...@googlegroups.com>

ReplyTo: gmail...@googlegroups.com

Subject: Re: [Gmail-Users] Spinning Wheel

[Andy]

> I don't want to misunderstand, Andy.  What "X"?  The only one I can think of
> (without using Chrome at this moment) would cause exiting from the page.

While a page is loading, or when you see the "spinning wheel" in the
tab, there is an "X" in the upper left of the toolbar, just to the
right of the two arrows (to go back or forward). Clicking on that "X"
stops further loading of the current page. The "X" turns into a
circular arrow ("reload") once the page is loaded.

It is not the smaller "X" in the tab itself, that closes the tab.

Andy

[DEP/Dodo]

I have now checked the spinning wheel issue on two computers at home.  Both have it, at least for a while.  On the desktop, it is not as intrusive as on the notebook.  ~Dodo

[DEP/Dodo]

Sorry--the only "X icons" I am aware of get me out of Gmail and Chrome.  One is at the upper right of the window (screen), and other is on the tab for this thread.  So, yes, clicking on either will stop loading because it closes the programs!  Somehow, I don't think this is the "X" both of you mean; however, it's all I know of.  
~Dodo

[Andy]

Sorry--the only "X icons" I am aware of get me out of Gmail and Chrome.

The one I was talking about is there ONLY while a page is loading.  On my screen it is immediately left of the "home" icon, to the left of the URL box.  (The "home" icon is not there by default in Chrome, but I enabled it.)

Andy

[DEP/Dodo]

Ah, excellent clarification.  Yes, when I click on the "X," the spinner stops and the "X" turns into a sideways arrow pointing to the right.  I don't understand how this works, but thank you for helping me stop the spinning.  I will check this out with my other computers, but it should work the same.
~Dodo

[DEP/Dodo]

Somehow I didn't see this reply until just now, well after your other also-helpful description.  ~Dodo

On Sat, Sep 3, 2011 at 6:56 AM, Andy <AI.e...@gmail.com> wrote:

While a page is loading, or when you see the "spinning wheel" in the
tab, there is an "X" in the upper left of the toolbar, just to the
right of the two arrows (to go back or forward).  Clicking on that "X"
stops further loading of the current page.  The "X" turns into a
circular arrow ("reload") once the page is loaded.

It is not the smaller "X" in the tab itself, that closes the tab.

Andy

[Marko Vukovic]

Hi D

Every web browser has some sort of status indicator. In Chrome, when it is waiting or receiving data from the remote server, you see the 'spinner'. The button to the right of 'back' and 'forward' becomes an X. This means 'stop loading'. When the data has been received, the button is circular with an arrow. This means 'reload the page'.

As Gmail contains scripts that make it an active web application and not just a static web page, I would expect some data sending and receiving from time to time, and therefore the 'spinner'.

I wouldn't worry too much about it.

On Sunday, September 4, 2011, DEP/Dodo wrote:

Ah, excellent clarification.  Yes, when I click on the "X," the spinner stops and the "X" turns into a sideways arrow pointing to the right.  I don't understand how this works, but thank you for helping me stop the spinning.  I will check this out with my other computers, but it should work the same.
~Dodo

Regards

--

Marko 

--
Marko

[DEP/Dodo]

On Sun, Sep 4, 2011 at 6:22 AM, Marko Vukovic <marko....@gmail.com> wrote:

Hi D

Every web browser has some sort of status indicator. In Chrome, when it is waiting or receiving data from the remote server, you see the 'spinner'. The button to the right of 'back' and 'forward' becomes an X. This means 'stop loading'. When the data has been received, the button is circular with an arrow. This means 'reload the page'.  This was also, along with Andy's, a clear explanation for which I thank you.  I never associated the spinning wheel with loading.  It was a distraction, more so on one of my computers and always and only with Chrome.  

As Gmail contains scripts that make it an active web application and not just a static web page, I would expect some data sending and receiving from time to time, and therefore the 'spinner'.  You recently posted another message about scripts.  I don't know anything about them and, as I have told you previously, I am not particularly technically savvy.  I know what I need to know or what I am interested in.  (You, a professional techie, were not pleased with that comment.)

I wouldn't worry too much about it.  Now that I know how to stop it, thanks to you and Andy, the annoyance and distraction are in the past.  ~Dodo

[DEP/Dodo]

My response  in the format I sent it does not appear clearly and cannot be easily read at this group's Website.  I won't do that again.  

To Marko's first paragraph, I responded:  This was also, along with Andy's, a clear explanation for which I thank you.  I never associated the spinning wheel with loading.  It was a distraction, more so on one of my computers and always and only with Chrome.

To his 2nd paragraph:  You recently posted another message about scripts.  I don't know anything about them and, as I have told you previously, I am not particularly technically savvy.  I know what I need to know or what I am interested in.  (You, a professionaltechie, were not pleased with that comment.)  

To his final paragraph:  Now that I know how to stop it, thanks to you and Andy, the annoyance and distraction are in the past.

Sorry for any inconvenience.  ~Dodo

[Marko Vukovic]

Hi D

Ok, so if you are not interested to know about what's going on then just be aware that if you interrupt the flow of data (ie. by clicking stop) then you are very likely to cause more problems for yourself.

--

Marko 

--
Marko

[DEP/Dodo]

Your comment below is important to me, Marko, as I didn't know that more problems could be caused, and I certainly don't want/need that!  Your specificity as to how the flow of data is interrupted, basic though it may be to others, is much appreciated.  The question then becomes:  How long do I allow the spinning wheel to spin . . . and spin . . . and spin?  ~Dodo

[Marko Vukovic]

What I would suggest Dodo is that you perform the usual clear cache and cookies then load up Gmail. Let it do it's spinning, maybe walk away for a cup of joe then come back. Hopefully by then it would be done. I would expect a bit of intermittent activity but if it is spinning continuously then there's a problem.

On Monday, September 5, 2011, DEP/Dodo wrote:

Your comment below is important to me, Marko, as I didn't know that more problems could be caused, and I certainly don't want/need that!  Your specificity as to how the flow of data is interrupted, basic though it may be to others, is much appreciated.  The question then becomes:  How long do I allow the spinning wheel to spin . . . and spin . . . and spin?  ~Dodo

--
Marko

[DEP/Dodo]

Every time I open Gmail???  

I can do e-mail while it's spinning.  Depending on which computer I'm using, the spinning is more or less noticeable and may or may not stop.  Again, I will try to be more alert to this. 
~Diane

[Marko Vukovic]

No not every time LOL, I just meant do it once and see if it makes a difference.

On Monday, September 5, 2011, DEP/Dodo wrote:

Every time I open Gmail???  

I can do e-mail while it's spinning.  Depending on which computer I'm using, the spinning is more or less noticeable and may or may not stop.  Again, I will try to be more alert to this. 
~Diane

--
Marko

[DEP/Dodo]

As you would know, Chrome gives the option as to how far back to go to clear cookies, etc.  What do you recommend?  

Also, I see on the computer I'm using (not my main desktop) no spinning wheel!  ~Dodo

[DEP/Dodo]

Just discovered something.  I am on the same computer and now have the spinning wheel again.  It apparently has to do with how I access Gmail (but always via Chrome).  For example, I have Gmail bookmarked and I have created a shortcut on my Desktop for it.  Perhaps I misspoke when I wrote earlier that the spinning wheel was gone.  That is the case while here on the composing page.  However, if I move the cursor anywhere else on this page, there it is.    Additionally, it is constantly spinning way up at the topmost left tab where this topic is identified with the red Gmail envelope icon.  Finally, this is happening even after clearing the cache and cookies as you suggested.  Know what?  I'm prepared to live with it if I have to.  At least everything works.

Ohmygosh!  It has suddenly stopped!  No more spinning anywhere!  Time-wise, that was quite a few minutes.  Superstition-wise, it happened just after I wrote of my readiness to live with it.  

Bottom line:  It seems to be a matter of time before it disappears.  Ironic that I discovered this while writing about it.  ~Dodo

[DEP/Dodo]

Which, of course, I don't want to do!  (If I were to click "stop," how long should I wait?)  As I wrote earlier this a.m., it took quite a few minutes on the computer I was using then for the spinning wheel to disappear.  On the Desktop computer I am using now, it was much quicker.  The good news is that in both instances, the spinner disappeared on its own.  I realize that means loading was completed.  ~Dodo

[Andy]

> be aware that if you interrupt the flow of data (ie. by clicking stop) then
> you are very likely to cause more problems for yourself.

While that may sometimes be true, I don't think it is always so, and
it doesn't seem to hurt in this case. Of course I could be wrong.

>  The question then becomes:  How long do
> I allow the spinning wheel to spin . . . and spin . . . and spin?  ~Dodo

Wait? Why wait? You can read and use the page even if the wheel
keeps on spinning. You don't need to wait for it to finish (or
perhaps to THINK that it is finished, even though it was really done
minutes ago). If you didn't know it was spinning, I think you'd be no
worse off.

It's not as if your CPU was running at 100% until the wheel stops spinning.

As "Click and Clack" (Tom and Ray from "Car Talk" on NPR radio) would
say, if it bothers you to see the wheel spinning, put some black tape
over it on your screen, and you'll be all set.

On my computer, whether it keeps spinning, and for how long, seems to
vary randomly. I don't see much reason to why it sometimes takes less
time.

Andy

[Michael Methot]

Umm, wow how did I miss this issue for so long. lol This was has already been rectified in the latest Beta. Still don't know what the issue was (I never found an official reply from the Gmail team on the changelog), but update here and the wheel of eternal loading will trouble you no more. :) http://www.google.com/landing/chrome/beta/

[Michael Methot]

P.S. It's a stable Beta, been using it for a week with no hiccups. 

[DEP/Dodo]

Marko:   be aware that if you interrupt the flow of data (ie. by clicking stop) then you are very likely to cause more problems for yourself.

Andy:  While that may sometimes be true, I don't think it is always so, and it doesn't seem to hurt in this case.  Of course I could be wrong.

Dodo:  If I recall correctly, Andy, Marko is a computer tech (Marko?), and I would rather be safe than sorry.

Dodo (earlier):  The question then becomes:  How long do  I allow the spinning wheel to spin . . . and spin . . . and spin? 

Andy:  Wait?  Why wait?  You can read and use the page even if the wheel keeps on spinning.  You don't need to wait for it to finish (or

perhaps to THINK that it is finished, even though it was really done

minutes ago).  If you didn't know it was spinning, I think you'd be no

worse off.  It's not as if your CPU was running at 100% until the wheel stops spinning.  As "Click and Clack" (Tom and Ray from "Car Talk" on NPR radio) would say, if it bothers you to see the wheel spinning, put some black tape over it on your screen, and you'll be all set.  On my computer, whether it keeps spinning, and for how long, seems to

vary randomly.  I don't see much reason to why it sometimes takes less

time.

Dodo:  I agree with not waiting, now that I have experienced I can work while it's happening.  As I have said, depending on where the cursor is, it can be distracting.  However, here on the composing page, it doesn't spin and, eventually, all spinning comes to an end, which is good.

[DEP/Dodo]

I am using Chrome 13.0.782.220 m.  Is this Beta?  If not, do I want Beta?  Or do I just want the automatic updates of Chrome as they occur?  Not totally confused (yet), I do understand that the "new and improved" offline Gmail is Beta.  ~Dodo

[DEP/Dodo]

Chrome Beta?  Besides apparently not having the spinning wheel (correct?), what are its features that Chrome 13.0.782.220 m doesn't have, pros and cons?  ~Dodo

[DEP/Dodo]

Still asking.  Anyone? (Who's impatient?)  ~Dodo

On Mon, Sep 5, 2011 at 7:31 AM, DEP/Dodo <depf...@gmail.com> wrote:

[Sean Murphy]

    If you know when the problem started, a little further back than that. If you are not sure, clear all.

[Sarah]

Hi Dodo,
What Michael appears to be saying is that the spinning wheel persisting in gmail for long periods was a bug, and that the problem has been fixed in a newer release of Chrome.
As others have explained, it's usually a normal part of a webpage loading, & on pages that actively exchange information with your computer at intervals, while you are using them, it will come and go. One of the occasions the spinning wheel appears is when synchronization is taking place. This is potentially one good reason to let it do it's thing & finish, & not to stop it.

On 6 Sep 2011 06:29, "DEP/Dodo" <depf...@gmail.com> wrote:
> *Still asking. Anyone? (Who's impatient?) **~Dodo*

>
> On Mon, Sep 5, 2011 at 7:31 AM, DEP/Dodo <depf...@gmail.com> wrote:

> *Chrome gives the option as to how far back to go to clear cookies, etc.
> What do you recommend? *

[Michael Methot]

Full list of updates from the Chromium change log. While I understand you are not all that tech savvy, I am posting it for other interested parties as well.

Basically this release contains fixes for a number of plugin stability issues and other bugs. No major design changes in this release.

98877	chrome-...@google.com	Incrementing VERSION to 14.0.835.124 M - /branches/835/src/chrome/VERSION
98876	jsc...@chromium.org	Merge 98875 - Fix unresponsive browser due to a crashed plugin with a modal dialog. If a plugin dies with an open modal window the browser window will not be enabled. So, we re-enable the browser if it's ever disabled without any child dialogs. BUG=90002 TEST=Kill the Flash process while a modal dialog (e.g. file, print) is open. Browser should remain responsive. Review URL: http://codereview.chromium.org/7812005 TBR=jsc...@chromium.org Review URL: http://codereview.chromium.org/7814001 M - /branches/835/src/chrome/browser/hang_monitor/hung_window_detector.cc
98874	cev...@chromium.org	Merge 98873 - Require Real Player 12.0.1.666 Corresponds to stability issues and also a security update: http://service.real.com/realplayer/security/08162011_player/en/ Review URL: http://codereview.chromium.org/7776019 TBR=cev...@chromium.org Review URL: http://codereview.chromium.org/7811007 M - /branches/835/src/webkit/plugins/npapi/plugin_list.cc
98862	c...@chromium.org	Merge 97732 - Try to catch dlls that crash the plugin process. - With a specific, forced dll eviction policy. Part of the code yellow BUG=none TEST=none Review URL: http://codereview.chromium.org/7670044 TBR=c...@chromium.org Review URL: http://codereview.chromium.org/7785004 M - /branches/835/src/content/common/sandbox_policy.cc
98843	z...@chromium.org	Merge 98758 - [Sync] Gracefully handle writing to a node when the cryptographer is not ready. Due to allowing users to configure without a passphrase if they don't have passwords enabled, we can get into a situation where we require encryption of datatypes, but don't have the cryptographer enabled. When in this situation we need to ensure we don't corrupt any data. Once the user sets their passphrase, we will reencrypt everything, which will overwrite unsynced entries with their encrypted versions, allowing the sync cycle to finish. BUG=93100 TEST=sync_unit_tests --gtest_filter="*GetCommitIdsFilterEntries*" Also to manually test: set up sync on a machine with an explicit passphrase. Set up sync without passwords enabled on a separate machine and don't enter the passphrase. Enable encryption on the first client. Attempt to add a bookmark on the second client. Review URL: http://codereview.chromium.org/7795002 TBR=z...@chromium.org Review URL: http://codereview.chromium.org/7802003 M - /branches/835/src/chrome/browser/sync/syncable/nigori_util.h M - /branches/835/src/chrome/browser/sync/engine/syncer_unittest.cc M - /branches/835/src/chrome/browser/sync/engine/get_commit_ids_command.cc M - /branches/835/src/chrome/browser/sync/engine/get_commit_ids_command.h M - /branches/835/src/chrome/browser/sync/syncable/nigori_util_unittest.cc M - /branches/835/src/chrome/browser/sync/syncable/nigori_util.cc
98841	ad...@chromium.org	Merge 96076 - Use MessageLoopProxy instead of MessageLoop to dispatch notifications in ObserverListThreadsafe. This is nearly identical to the reverted r96013, with the modification that std::map::insert isn't used. Its invocation was complex (such that it worked in some compilers but not in others) and the performance gain is negligible in any use case I've seen in Chromium. BUG=91589 Review URL: http://codereview.chromium.org/7604006 TBR=ad...@chromium.org Review URL: http://codereview.chromium.org/7792046 M - /branches/835/src/base/observer_list_threadsafe.h M - /branches/835/src/base/observer_list_unittest.cc
98838	tba...@chromium.org	Merge 98292 - Show only one error notification per inserted mulitpartitioned usb card. iWe should use system path of the device that contains partitions block device, instead partitions system path as notifications identification path. e.g. /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/host9/target9:0:0/9:0:0:0 instead of /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/host9/target9:0:0/9:0:0:0/block/sdb/sdb9 TEST=Manual on Cr48 (tried multiple-partitioned device with no good partitions, with one good-partition, device with one partition) BUG=chromium-os:19559 Review URL: http://codereview.chromium.org/7748003 TBR=tba...@chromium.org Review URL: http://codereview.chromium.org/7803003 M - /branches/835/src/chrome/browser/chromeos/extensions/file_browser_event_router.cc
98837	sh...@chromium.org	Merge 98285 - [Mac] Keep the page-info-bubble controller alive until done with layout. If the window is animating closed when a previously-posted PerformLayout task is fired, the last reference to the controller may be released while laying things out. Pin the controller down until the task is completed. BUG=90773 TEST=Monitor crash server for continued zombies. Review URL: http://codereview.chromium.org/7717027 TBR=sh...@chromium.org Review URL: http://codereview.chromium.org/7795022 M - /branches/835/src/chrome/browser/ui/cocoa/page_info_bubble_controller.mm
98832	van...@chromium.org	Merge 98772 - Fix regression in printing page settings CSS properties. PrintWebViewHelper::GetPageSizeAndMarginsInPoints may update PrintMsg_Print_Params, so we must call UpdatePrintParams after that. BUG=94294 TEST=Described in bug - print a page with page margin CSS. Review URL: http://codereview.chromium.org/7794010 TBR=van...@chromium.org Review URL: http://codereview.chromium.org/7794024 M - /branches/835/src/chrome/renderer/print_web_view_helper.cc
98802	se...@google.com	Merge 94081 - Fixed slider thumb in the mediaplayer progress (issue 7488055). BUG=chromium-os:17030, chromium-os:17524 TEST=None Review URL: http://codereview.chromium.org/7781006 M - /branches/835/src/chrome/browser/resources/file_manager/mediaplayer.html
98800	dgo...@chromium.org	Merge 98618 - [chromeos] Do not move notifications to KEEP_SIZE state when mouse moved. This allows notification to resize. BUG=chromium-os:16050 TEST=See bug. Review URL: http://codereview.chromium.org/7747044 TBR=dgo...@chromium.org,osh...@chromium.org Review URL: http://codereview.chromium.org/7795017 M - /branches/835/src/chrome/browser/chromeos/notifications/notification_browsertest.cc M - /branches/835/src/chrome/browser/chromeos/notifications/notification_panel.cc
98799	dgo...@chromium.org	Merge 97620 - [filebrowser] Enable fileBrowserHandlers only for files, not directories. BUG=chromium-os:18397 TEST=See bug. Review URL: http://codereview.chromium.org/7697014 TBR=dgo...@chromium.org,rgi...@chromium.org Review URL: http://codereview.chromium.org/7799020 M - /branches/835/src/chrome/browser/resources/file_manager/js/file_manager.js
98784	chrome-...@google.com	Incrementing VERSION to 14.0.835.123 M - /branches/835/src/chrome/VERSION
98773	z...@chromium.org	Revert 98770 - Merge 98758 - [Sync] Gracefully handle writing to a node when the cryptographer is not ready. Due to allowing users to configure without a passphrase if they don't have passwords enabled, we can get into a situation where we require encryption of datatypes, but don't have the cryptographer enabled. When in this situation we need to ensure we don't corrupt any data. Once the user sets their passphrase, we will reencrypt everything, which will overwrite unsynced entries with their encrypted versions, allowing the sync cycle to finish. BUG=93100 TEST=sync_unit_tests --gtest_filter="*GetCommitIdsFilterEntries*" Also to manually test: set up sync on a machine with an explicit passphrase. Set up sync without passwords enabled on a separate machine and don't enter the passphrase. Enable encryption on the first client. Attempt to add a bookmark on the second client. Review URL: http://codereview.chromium.org/7795002 TBR=z...@chromium.org Review URL: http://codereview.chromium.org/7795016 TBR=z...@chromium.org Review URL: http://codereview.chromium.org/7806005 M - /branches/835/src/chrome/browser/sync/syncable/nigori_util.h M - /branches/835/src/chrome/browser/sync/engine/syncer_unittest.cc M - /branches/835/src/chrome/browser/sync/engine/get_commit_ids_command.cc M - /branches/835/src/chrome/browser/sync/engine/get_commit_ids_command.h M - /branches/835/src/chrome/browser/sync/engine/syncapi.cc M - /branches/835/src/chrome/browser/sync/syncable/nigori_util_unittest.cc M - /branches/835/src/chrome/browser/sync/syncable/nigori_util.cc
98770	z...@chromium.org	Merge 98758 - [Sync] Gracefully handle writing to a node when the cryptographer is not ready. Due to allowing users to configure without a passphrase if they don't have passwords enabled, we can get into a situation where we require encryption of datatypes, but don't have the cryptographer enabled. When in this situation we need to ensure we don't corrupt any data. Once the user sets their passphrase, we will reencrypt everything, which will overwrite unsynced entries with their encrypted versions, allowing the sync cycle to finish. BUG=93100 TEST=sync_unit_tests --gtest_filter="*GetCommitIdsFilterEntries*" Also to manually test: set up sync on a machine with an explicit passphrase. Set up sync without passwords enabled on a separate machine and don't enter the passphrase. Enable encryption on the first client. Attempt to add a bookmark on the second client. Review URL: http://codereview.chromium.org/7795002 TBR=z...@chromium.org Review URL: http://codereview.chromium.org/7795016 M - /branches/835/src/chrome/browser/sync/syncable/nigori_util.h M - /branches/835/src/chrome/browser/sync/engine/syncer_unittest.cc M - /branches/835/src/chrome/browser/sync/engine/get_commit_ids_command.cc M - /branches/835/src/chrome/browser/sync/engine/get_commit_ids_command.h M - /branches/835/src/chrome/browser/sync/engine/syncapi.cc M - /branches/835/src/chrome/browser/sync/syncable/nigori_util_unittest.cc M - /branches/835/src/chrome/browser/sync/syncable/nigori_util.cc
98753	chrome-...@google.com	Incrementing VERSION to 14.0.835.122 M - /branches/835/src/chrome/VERSION

--

[Michael Methot]

Yes, use this link to download the beta build version 14.0.835.126 beta-m http://www.google.com/landing/chrome/beta/ --

This is a very stable release, I have been using it extensively for a variety of purposes for the last week with no hiccups. It will solve your issue.

--

[Michael Methot]

I can't nail anything down that is concrete, but yes, it appears to have been a bug. Whatever the reasons, Version 14 is as stable as it's going to get, the spinning throbber issue is resolved, and I would recommend everyone update to take advantage of the latest fixes and security improvements. Let's shut this thread down and move on folks.

Cheers

[DEP/Dodo]

Thank you, Sean.  The spinning wheel no longer is an issue for me since I now know it will disappear sooner or later.  Also, as the group has said, it can be ignored.  What about just for "general housekeeping"?  From your post, it would appear to be from the "beginning of time," which is what I've been doing.  ~Dodo

On Tue, Sep 6, 2011 at 2:15 AM, Sean Murphy <smpa...@gmail.com> wrote:

    If you know when the problem started, a little further back than that. If you are not sure, clear all.

[DEP/Dodo]

You make good sense, Sarah.  ~Dodo

[Bradley Curtis]

Hello guys & Gals

I would like to ask a question about the "spinning wheel"  I currently have Chrome version 13.0.782.220  which I thought was the latest available. If this truly was a "bug" that was fixed, then is it reasonable to have this spinning wheel continue on for 32 minutes? That was the last timing made today Sept 7th.

Respectfully,

Brad Curtis

--

[Sarah]

The version that Michael mentioned was 14.something. Check out his posts in this thread & the links.
The inference is that the problem has been fixed in a later release.

On 8 Sep 2011 02:31, "Bradley Curtis" <bcur...@gmail.com> wrote:
> Hello guys & Gals
> I would like to ask a question about the "spinning wheel" I currently have
> Chrome version 13.0.782.220 which I thought was the latest available. If
> this truly was a "bug" that was fixed, then is it reasonable to have this
> spinning wheel continue on for 32 minutes? That was the last timing made
> today Sept 7th.
>
> Respectfully,
> Brad Curtis
>
> On Tue, Sep 6, 2011 at 9:58 PM, DEP/Dodo <depf...@gmail.com> wrote:
>

>> *You make good sense, Sarah. **~Dodo*

[Sarah]

However version 14.whatever is a beta release (see Michael's posts & links in this thread), so is something you have to go get, you will not receive it as an automatic update.
Apologies for not quoting or linking, the gmail mobile app is rather limited in that respect. I think I will have to revert to gmail website; the app has improved but still falls short for me.

[DEP/Dodo]

Good info.  Thanks, Sarah.  ~Dodo

On Tue, Sep 6, 2011 at 4:02 AM, Sarah <mail...@gmail.com> wrote:

[brosselle]

This issue has already been beat to death. It's resolved in v14.

http://code.google.com/p/chromium/issues/detail?id=85248


On Sep 5, 10:31 am, "DEP/Dodo" <depfah...@gmail.com> wrote:
> *As you would know, Chrome gives the option as to how far back to go to
> clear cookies, etc.  What do you recommend?  *
> *
> *
> *Also, I see on the computer I'm using (not my main desktop) no spinning
> wheel!  **~Dodo*

[Michael Methot]

Damn brosselle, how did you find that? I spent HOURS searching for it. :/ At least you found the bug report, still doesn't explain what the actual issue was. And yes, it has been beat to death. Upgrade to version 14 and let's put it behind us folks!!

Clicky clicky clicky and let's find something new to talk about. :) http://www.google.com/landing/chrome/beta/

[Bradley Curtis]

Thanks I got Chrome latest beta release 14...and all is well

Brad

[DEP/Dodo]

Even though there have been two suggestions from two people (on 9/6 and 9/8) to conclude this thread, you have opted to continue it, with which I have no problem.  These posts usually are self-limiting based on the posters' interest.   However, in another thread, when others continued to post, you blamed the thread's originator for somehow being responsible.  Hmmm.  ~Dodo