Hello, I'm the main CCW developer. I have double checked the source code, and can confirm that the save mechanism is handled by Eclipse. So one can expect it to be as stable as every other save action performed in the Eclipse IDE.
There are a number of listeners that are triggered after the Save action has completed. It's most probably after the save, and presumably inside one of those listeners, that the hang occured. A central goal of CCW is to be as stable as possible. So if you are able to describe how to deterministically reproduce the issue, then please create an issue and put the description there. Also, if you can attach the workspace's .metadata/.log file, I can take a look at it. Link for creating a new issue : https://code.google.com/p/counterclockwise/issues/entry Please try to adopt a neutral language, leaving out the sarcasms and implicit/explicit injonctions, etc. Those are totally inappropriate. Being a "user" of a "service" does not give you the right to act like that. To that matter, it is even irrelevant that the service is paid for, or free. I know not everybody is equal with regards to how to best communicate, but it can be learned. Listen to the advices given in this thread. Cheers, Laurent 2014-10-26 3:38 GMT+01:00 Fluid Dynamics <a2093...@trbvm.com <javascript:_e(%7B%7D,'cvml','a2093...@trbvm.com');>>: > Would somebody mind explaining to me why I just had CCW 0.28.1.STABLE001 > hang with 100% CPU usage when I edited this line: > > := (= v cr)))) > > to this: > > = (= v cr)))) > > and then hit control-S? > > I do not ever want to see anything purportedly "STABLE" do something like > that ever again, and that goes *one trillionfold* if it's IN THE MIDDLE OF > A GODDAMN SAVE. What if my file had been corrupted, or truncated and only > the first 42 bytes of the new version written thus far, or something like > that at the moment when the hang started? Fortunately, in this instance > that had not happened and the file seems to have been saved completely just > *before* the hang. I might not be so lucky next time. That is why this > cannot be permitted to happen again, and why therefore an explanation is > required, and urgently, that I might be perfectly able to avoid triggering > this severe, showstopping, and inexcusable bug again until such time as an > 0.29.1 is published that has it permanently fixed. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > <javascript:_e(%7B%7D,'cvml','clojure@googlegroups.com');> > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > <javascript:_e(%7B%7D,'cvml','clojure%2bunsubscr...@googlegroups.com');> > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com > <javascript:_e(%7B%7D,'cvml','clojure%2bunsubscr...@googlegroups.com');>. > For more options, visit https://groups.google.com/d/optout. > -- Laurent Petit -- Laurent Petit -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
