Mac Build 37102 broken?

[Jason Allen]

I updated to build 37102 of the Mac OS X version of Chromium this
morning and it appears to be completely broken on my system. All
plugins and extensions crashed as soon as I launched it, and doing a
complete uninstall/reinstall does not fix the problem.

I am trying to figure out how to create a whole new user profile
(though my uninstall should have removed it) in case my original one
is corrupted but all I can find are Windows instructions (grrrr).

At this point my copy of Chromium is unusable and refuses to render a
single page, giving the Aww Snap error.

Chromium was working fine last night, and no changes have been made to
my OS.

Anyone have any suggestions? Many, many thanks in advance!

[PhistucK]

You should use the terminal (I am speaking on the fly here, because I do not have Macintosh and I do not know how to use it, I just remember seeing samples in this regard) to run Chromium through shell.

Type the regular command you need to type to load it, but add -

--user-data-dir="full_path_to_a_new_empty_or_non_existent_folder"

At the end of it.

I hope that works and makes sense.

☆PhistucK

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-discuss

[Jason Allen]

Tried this and it still fails when pointing to a new user directory.
I still get the Awww Snap page failed error message on every single
site I try to visit. There is no delay before the error appears, like
it isn't even trying or something is very broken.

- Jason

On Jan 26, 11:01 am, PhistucK <phist...@gmail.com> wrote:
> You should use the terminal (I am speaking on the fly here, because I do not
> have Macintosh and I do not know how to use it, I just remember seeing
> samples in this regard) to run Chromium through shell.
> Type the regular command you need to type to load it, but add -
> --user-data-dir="full_path_to_a_new_empty_or_non_existent_folder"
> At the end of it.
>
> I hope that works and makes sense.
>
> ☆PhistucK
>
>
>
> On Tue, Jan 26, 2010 at 17:47, Jason Allen <jasonral...@gmail.com> wrote:
> > I updated to build 37102 of the Mac OS X version of Chromium this
> > morning and it appears to be completely broken on my system.  All
> > plugins and extensions crashed as soon as I launched it, and doing a
> > complete uninstall/reinstall does not fix the problem.
>
> > I am trying to figure out how to create a whole new user profile
> > (though my uninstall should have removed it) in case my original one
> > is corrupted but all I can find are Windows instructions (grrrr).
>
> > At this point my copy of Chromium is unusable and refuses to render a
> > single page, giving the Aww Snap error.
>
> > Chromium was working fine last night, and no changes have been made to
> > my OS.
>
> > Anyone have any suggestions?  Many, many thanks in advance!
>
> > --

> > Chromium Discussion mailing list: chromium-disc...@chromium.org

[PhistucK]

Did you try to backup your current profile directory, remove it and then start Chrome?

Maybe the build is simply faulty, there are no guarantees in Chromium.

☆PhistucK

Chromium Discussion mailing list: chromium...@chromium.org

[Jason Allen]

My bookmarks are syncing and I don't run more than a couple
extensions, so I don't really care about my old profile. I deleted it
when I tried the original reinstall before I posted this request for
help.

*Shrugs* Guess I'll just wait for another build to come out. I update
chromium at least once a day and have never had a problem like this
before.

Thanks

- Jason

[PhistucK]

Well, you had luck, then.

I remember the first time I downloaded a Chromium build, it did not even start up. Later I found out that that specific build did not pass the startup test.

☆PhistucK

Chromium Discussion mailing list: chromium...@chromium.org

[Jason Allen]

Sadly confirmed. Build 37102 appears to be broken.

I have installed/tested/uninstalled the 5 builds prior to 37102 and
they all work fine. This is after a complete uninstallation
(including user profile directories, basically everything in
Application Support) between build tests.

37101 is the last working build according to what I am seeing. I also
tried restarting my macbook completely (believe it or not this fixed a
chromium issue several months ago) and that did not fix anything.