Re: Still crashing - Uncle Asad

Have you filed a bug report? Developers cannot fix crashes they are not aware of, and most users do not seem to be crashing.

Reply to This

Thursday, April 24 2008 @ 10:23 PM PDT

Still crashing - MacGuffin

Well, this isn't good news. :(
One of Camino's main draws for me is the ability to configure cookie acceptance. Why would the developers eliminate this all-important feature? It seems to me that they should be concentrating on providing a faster, stabler browser, not eliminating its strong points.
I agree that bug reports should be filed, but I should hope that developers would also keep an eye on VT feedback as well and take the opportunity to respond to the concerns of a wider audience.

Reply to This

Friday, May 02 2008 @ 06:01 AM PDT

Still crashing - s_morgan

> Why would the developers eliminate this all-important feature?

We didn't. Camino 1.6 didn't remove any cookie handling features.

Reply to This

Tuesday, May 20 2008 @ 03:31 PM PDT

Still crashing - mr sniffles

Yeah, 1.6 is completely crash crazy on both my Titanium and my iBook. In fact, it would often refuse to even launch on the Titanium (and when it did, it would crash soon thereafter)

Luckily, I found a really old version (1.0.2) that seems to work a lot better than the most recent. It's sad to see my favorite browser become unusable. I hope this is rectified quickly.

Reply to This

Tuesday, May 20 2008 @ 12:11 PM PDT

Still crashing - s_morgan

As Uncle Asad said, we can't fix crashes that we don't know anything about--and contrary to popular belief, we do actually check that Camino works for a wide variety of people before we release it, so if it's continuously crashing for you, you can assume that we (and by extension, everyone testing pre-release versions of Camino and reporting issues to us) haven't seen that crash, or we wouldn't have released.

If you file a bug we'll be more than happy to investigate the issue, but just posting here that it's crashing all the time for you and hoping a future release will resolve the issue is like calling a mechanic to say that your car doesn't run, then waiting for your car to start working.

Reply to This

Tuesday, May 20 2008 @ 03:41 PM PDT

Still crashing - MacGuffin

Bad analogy--whether we post here or contact Camino direct, we're not "bringing the browser in" for repair--we're notifying you (and, thanks to VT, everyone else). By posting grievances (or kudos) here, we're not only notifying the developers, we're communicating with other users as well. I think most of us are disinclined to repeat ourselves, especially given that we download from VT and not the Camino Web site.
In a similar vein, I should think that the developers would prefer to address their responses to a wider audience rather than to one disgruntled user at a time.

Reply to This

Wednesday, May 21 2008 @ 03:39 AM PDT

Still crashing - s_morgan

Our bug reporting system is designed to facilitate asking the sort of follow-up questions we need in order to actually investigate problems, and has tools for necessary activities like attaching crash logs to reports, so is not unlike like bringing a car in to a mechanic. On the other hand, there is absolutely no chance that we can debug a crash from the statement "Camino crashes", without any reasonable way to follow up, and VersionTracker is not set up to make follow up and detailed investigation of crashes feasible. An analogy doesn't have to be perfect to be useful.

The only reasonable response we can make here is to let people know how to follow up with us to get crashes looked into, so that is what we do.

Reply to This

Wednesday, May 21 2008 @ 07:18 AM PDT

Still crashing - mr sniffles

I reported the crashes as they happened (I, of course, stopped using the browser after a period, as I need a web browser for things other than reporting it's crashes)

That said, I also reiterated the crash problems here, as to warn other potential users, and for them to perhaps wait for a more stable release (assuming that they use web browsers for things other than crash reporting, as well)

That's what the feedback function is for, to let others know how well the software works. It really has nothing to do with bug reporting.

And while I'm sure you don't want to release a piece of faulty software (does anyone?), by looking at my experiences and the experiences of others, it seems you did just that. I feel it's my responsibility to report these problems to the developer(s), but I also feel it's my responsibility to warn others so they may be able to avoid the problems altogether.

Reply to This

Wednesday, May 28 2008 @ 10:02 PM PDT