Skip site navigation (1)Skip section navigation (2) 
Date:      Thu, 16 Jan 2014 23:11:06 -0500
From:      Thomas Hoffmann <trh411@gmail.com>
To:        freebsd-ports@freebsd.org
Subject:   Re: chromium 32.0.1700.77 behaving badly
Message-ID:  <CAB7-odm0r__mQ4MPiaHtfCFsz5sW_kZpLW7c%2B5Cy0-ok1pAcQA@mail.gmail.com>
In-Reply-To: <CAB7-odmN1RbmnDszcnrj3qx8W0dJT9=zBM8wqk-BPvo5GmTeAg@mail.gmail.com>
References:  <CAB7-odmN1RbmnDszcnrj3qx8W0dJT9=zBM8wqk-BPvo5GmTeAg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help 
My apologies for the noise. I realized after sending that it should have
been directed at freebsd-chromium.


On Thu, Jan 16, 2014 at 11:03 PM, Thomas Hoffmann <trh411@gmail.com> wrote:

> Just upgraded chromium from source to 32.0.1700.77. When I select anything
> from the Chrome menu that opens a new tab, closing that tab results in a
> segmentation fault. I tried Bookmarks Manager, Settings, About and Help all
> with the same results. Other tabs behave properly and just go away when
> closed. Anyone else seeing this?
>
> I'm on FreeBSD-10.0.RELEASE r260689 amd64.
>
> I ran the debugger on the core file, but the info does seem to be of any
> use.
>
> (gdb) core chrome.core
> Core was generated by `chrome'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x00000000007f3f44 in ?? ()
> (gdb) bt
> #0  0x00000000007f3f44 in ?? ()
> #1  0x00007fffffffbe70 in ?? ()
> #2  0x000000000086a63b in ?? ()
> #3  0x0000000810426200 in ?? ()
> #4  0x000000081523d6b8 in ?? ()
> #5  0x00007fffffffbea0 in ?? ()
> #6  0x00000000025d849a in ?? ()
> #7  0x0000000005664060 in ?? ()
> #8  0x000000081523d680 in ?? ()
> #9  0x00000008151ab970 in ?? ()
> #10 0x00000008153e85d8 in ?? ()
> #11 0x00007fffffffbec0 in ?? ()
> #12 0x00000000025d838e in ?? ()
> #13 0x0000000005664060 in ?? ()
> #14 0x00000008153e8560 in ?? ()
> #15 0x00007fffffffbef0 in ?? ()
> #16 0x0000000002741f02 in ?? ()
> #17 0x0000000000000025 in ?? ()
> #18 0x00000008151ab920 in ?? ()
> #19 0x00000008104ed2d0 in ?? ()
> #20 0x0000000816b819d0 in ?? ()
> #21 0x00007fffffffbf10 in ?? ()
> #22 0x0000000002740c18 in ?? ()
> #23 0x00000000054b2920 in ?? ()
> #24 0x00000008151ab920 in ?? ()
> #25 0x00007fffffffbf30 in ?? ()
> #26 0x0000000002740b7e in ?? ()
> #27 0x00000000054b2920 in ?? ()
> #28 0x0000000816976e80 in ?? ()
> #29 0x00007fffffffbf60 in ?? ()
> #30 0x00000000025525cf in ?? ()
> #31 0x0000000816b819d0 in ?? ()
> #32 0x00000008104ed290 in ?? ()
> #33 0x00000008104ed2d0 in ?? ()
> #34 0x00000008104ed278 in ?? ()
> #35 0x00007fffffffbf80 in ?? ()
> #36 0x000000000255257e in ?? ()
> #37 0x00000000054a7070 in ?? ()
> #38 0x0000000816a44de0 in ?? ()
> #39 0x00007fffffffbfa0 in ?? ()
> #40 0x0000000002740bfb in ?? ()
> #41 0x00000000054b2920 in ?? ()
> #42 0x0000000816a44de0 in ?? ()
> #43 0x00007fffffffbfc0 in ?? ()
> #44 0x0000000002740b7e in ?? ()
> #45 0x00000000054b2920 in ?? ()
> #46 0x0000000000000000 in ?? ()
>
> Any way I can make the back trace show more useful info? What other info
> can I provide to help? Should I open a PR?
>

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB7-odm0r__mQ4MPiaHtfCFsz5sW_kZpLW7c%2B5Cy0-ok1pAcQA>