gliaskos / freebsd-chromium Goto Github PK

When installing the most recent port of Chromium, my, er, browser chrome gets horribly garbled:

http://eigenstate.org/tmp/borked-chrome.png

The web content is unaffected. The previous version (51.0.2704.84) did not have this issue, although I upgraded it at the same time as my nvidia drivers among other packages, so I'd be willing to believe theese are the cause of the issue. I'm currently downgrading to verify that the older version still works.

I've attempted turning off hardware acceleration in the UI, and it doesn't seem to affect things.

Some additional possibly useful information:

$ uname -a
FreeBSD oneeye 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44 UTC 2016     [email protected]:/usr/obj/usr/src/sys/GENERIC  amd64

And in case the nvidia version matters:

$  nvidia-xconfig --version
nvidia-xconfig:  version 367.35  (root@oneeye)  Thu Aug  4 20:18:01 PDT 2016

I've got 4k monitors, so if there's something broken with hidpi, that might be the root cause -- I noticed some changes to that when looking over the diff updating the code.

If there's anything I can do to help debug, let me know.

In the internal Task Manager the Memory footprint column doesn't show:

At my repository https://github.com/LeFroid/chromium/ , while porting chromium over to version 41 there were a few patches I added from OpenBSD's port repository - this related mostly to chromium's move from using gtk+ to aura/ash/gtk/etc , but it also included some interface changes such as the ability to switch tabs by scrolling with the mouse.

I hand-picked the patches that were needed to keep this functionality in chromium 42 and applied it to my branch. Since it is not a fork of this one, however, I could not make a PR easily so I put the changes here on pastebin: http://pastebin.com/GxQnsku6

They will cause no regressions and only add some minor aesthetic features so I think it would be nice to have in the official port.

καλημερα συνδεσα το vivawallets με το eshop μου περασσα κωδικουσ api,source code και merchant id dokimazw tin karta mou pou exei xrimata mou kanei redirect pou exw zitisei stin viva kai mou leei h sunalagi apetuxe ti kanw?

Hello,

Hangouts screen sharing doesn't work due to the compile option
enable_hangout_services_extension=true
missing from the Makefile and no option available.

Could this be added so that default behavior is to have working screen sharing?

Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1389708

Thanks

I'm trying to use Chrome extensions that interact with USB devices, like Trezor or Ledger wallets, but chrome crashes as soon as they try to connect.

You can easily reproduce the issue by simply installing the extension at https://wallet.trezor.io (no need to have any device)

I'm not sure what happened, but I get lots and lots of "black boxes" in most web pages and a tab crash every few seconds.
(previously, I had tab hanging, not crashing, many times a day, but not many times per minute)

In the console, I see a lot of:

[2606:509698048:0307/121124.219342:ERROR:gles2_cmd_decoder.cc(17292)] [.CompositorWorker-0x82885f600]GL ERROR :GL_INVALID_VALUE : glCopySubTextureCHROMIUM: source texture has no data for level

Followed by a single:

[6681:551614720:0307/121214.434132:ERROR:broker_posix.cc(46)] Received unexpected number of handles

And also lots of:

[2606:509698048:0307/121812.161296:ERROR:gles2_cmd_decoder.cc(9881)] [.DisplayCompositor-0x82966e000]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[2606:509698048:0307/121812.161313:ERROR:logger.cc(47)] Too many GL errors, not reporting any more for this context. use --disable-gl-error-limit to see all errors.
[2594:509698048:0307/121812.180148:ERROR:navigation_entry_screenshot_manager.cc(135)] Invalid entry with unique id: 170

Hi fellows,

I think that the freebsd-chromium wiki [1] needs to be updated. The main purpose would be to report the current status of the chromium bugs, add the new contributors and clean up old links.

[1] https://wiki.freebsd.org/Chromium

What do you think about this proposal?

Some feedback about this would be great.

Carlos J.

Since 2-3 versions I'm needing to re-login from scratch to any Google service, and Github, and others, each time I open the browser. Is it only me, or is it a regression?
PS: I still have to try deleting and re-importing the profile, which sometimes helps with stuff like this (but having to migrate the lots of open tabs is stopping me from doing it now).

Hi,

44.0.2403.104 was working pretty well. Almost back to normal with downloads working, plugin installation, and the occasional Aw, snap! crash. 44.0.2403.125 won't even pull up a window for me. If I run chromium it forks, returns 0, and spins and spins doing nothing (_sysctl in truss -fp), never coming up. This is on 10.1-RELEASE. I went back to 104 and it came up.

Can anyone else confirm this behavior?

Thank you,
Teran

Hi everyone,

First off, thank you for porting this over. I'm sure it's a rather tricky one to get right and generally Chrome has been very stable for me on FreeBSD. That's at least a year or so, until now.

Since the latest pkg upgrade I've been having continual Aw, snap! errors. Happens on LinkedIn, HipChat, and others. They range from 9/10 to maybe 1/50 page loads. I know little about them and am not sure if this is the place to report it, but am hoping you guys see something similar and know what's going on, or have suggestions on how I can best debug it.

My Chromium version is 43.0.2357.65. I'm on FreeBSD 10.1-RELEASE, x86_64.

Thank you,
Teran

As mentioned in the title, visiting kickstarter.com will reliably segfault Chromium.

Currently on Version 51.0.2704.84 (64-bit) because of the previously filed issue with yellow blobs blanking out the navigation bar.

There is no sound in chrome from this repo (recent build of chromium-54.0.2840.100) on freebsd-current
Chrome itself works fine, much smoother than 51.x from ports, but no sound on youtube and other sites. Can provide additional info on request.

Everything is in the title.

Installed chromium, connected with a google account.
Sync internals tells that the last sync happened 5,114 hours, 44 minutes ago.

Request Start button does nothing
Trigger GetUpdates button does nothing.

It would be nice to keep the upstreaming effort to minimize the divergence.

For example, a file used in BSD is recently garbage collected because it cannot be reached from any GN files upstream. Ref: https://codereview.chromium.org/2876623002/

obj/third_party/ffmpeg/libffmpeg.a(ffmpeg.h264chro): In function ff_h264chroma_init': h264chroma.c:(.text.unlikely.ff_h264chroma_init+0xb7): undefined reference toff_h264chroma_init_x86'
obj/third_party/ffmpeg/libffmpeg.a(ffmpeg.h264dsp.): In function ff_h264dsp_init': h264dsp.c:(.text.unlikely.ff_h264dsp_init+0x1fa): undefined reference toff_h264dsp_init_x86'
obj/third_party/ffmpeg/libffmpeg.a(ffmpeg.h264qpel): In function ff_h264qpel_init': h264qpel.c:(.text.unlikely.ff_h264qpel_init+0x18b6): undefined reference toff_h264qpel_init_x86'
obj/third_party/ffmpeg/libffmpeg.a(ffmpeg.autorena): In function ff_mpadsp_init': autorename_libavcodec_mpegaudiodsp.c:(.text.unlikely.ff_mpadsp_init+0x77): undefined reference toff_mpadsp_init_x86'
obj/third_party/ffmpeg/libffmpeg.a(ffmpeg.dct.o): In function ff_dct_init': dct.c:(.text.unlikely.ff_dct_init+0x1b5): undefined reference toff_dct_init_x86'
obj/third_party/ffmpeg/libffmpeg.a(ffmpeg.sbrdsp.o): In function ff_sbrdsp_init': sbrdsp.c:(.text.unlikely.ff_sbrdsp_init+0x94): undefined reference toff_sbrdsp_init_x86'
collect2: error: ld returned 1 exit status

Second Edit, 2017-01-11: I have withdrawn my expired bounty. Just $57 in the pot at the moment.

First edit: I haved moved and doubled my bounty from a personal one to BountySource. This now expires early/mid next year instead of by the end of the year.

Hi,

Chromium on FreeBSD has been extremely unusable for months. I get these pages every several clicks. Firefox, is far too slow. surf, is too slow. Chromium is fast and works great, aside from the random crashes.

I'd rather use Chromium and it's killing me.

1BTC to someone who can provide a reliable (and not for just the next version, ideally patched upstream), current stable Chromium on FreeBSD 10.2, as installed by pkgng. This expires at the end of the year. Does not apply for odd settings hacks, patches that break other things, things that don't work out of the box.

I am using x86_64. I have a new Chromium every start with a set master_preferences which I can provide if needed. This should be very reproducible, from what I've found. Let me know if you have any trouble reproducing it. I'll want to confirm for a couple days that I see no more of these when browsing. Currently, it's about one every five minutes of normal browsing, with a few in succession, and then going away entirely for a little bit. I'd also like a description of the cause and fix.

This is regarding issue #14.

Thank you!

--Teran

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200601

It's been a long time since the last «Aw, snap» error, but lately I'm having a lots of problems loading a few websites (e.g. Facebook, Google Plus, I guess it might be something regarding intensive AJAX usage, but also happens on random "light" pages, less frequently); the page never loads (and the icon in the tab continues spinning) or the page loads but then stops after a very small time (doesn't click on links, doesn't scroll).

I'm using version 52.0.2743.116 (64-bit) as installed with pkg install chromium on FreeBSD 10.3-RELEASE-p4.

Happens to anyone else or should I check my installation more?

PS: I added 127.0.0.2 www.kickstarter.com to /etc/hosts to avoid those crashes.

USB devices are present and with correct permissions, but Chrome WebUSB API implementation cannot find anything.

Neither casting tabs or desktops works as chrome can't find any chrome cast devices on network. (visibility of chromecast verified from other devices on network.)

No crashes happen just cant find any devices.

Not able to find any pertinent debug information at this time.

Current Version:
Version 71.0.3578.98 (Official Build) (64-bit)

Will test on chrome 72 as soon as it's in Project Trident(trueos desktop)

Hi everyone,

After the latest patches, I installed the update. I cannot install Chrome plugins now (at least the Okta one). I did have one crash on the plugin install page. Also, like before, idle CPU is around 100% even though the browser is generally responsive.

Are there any test cases around Chrome? I'm interested in building out a platform to test it, or at least some test cases where Chrome navigates and gets checked for crashes, ideally put into Travis or something like it.

Lastly, can you sign up this project for https://tip4commit.com/ ? I'd like to sponsor the project.

Thank you,
Teran

I wasn't expecting auto-upgrade from a pkg… it erroneously says it has been updated and needs a reload:

pressing the button it restarts, but o course with the same exact version (being installed by pkg and owned by root, of course).
I think the warning should just be disabled.

now that chromium 60 is available, any word when we can expect port update? thanks.

I've installed Chromium through pkg, and it seems to work fine when I start it up. However, when I log into my Google account (to sync my extensions, settings, bookmarks, etc.), I start continually getting notifications that each of my extensions has crashed (cycling through them, so even when closing them, new ones pop up). Even worse, I'm no longer able to load any webpages; the current page (or any new tab I open) is blank, and when I type something into the URL bar and hit enter, the page appears to reload, but it still just shows a blank screen.

I'm currently using the March snapshot 11.0-CURRENT and Chromium 49.0.2623.110, although I tried and had the same results with FreeBSD 10.3. Any idea if there's some way I can fix this, or is it not supported at this time?

The "End" key does nothing at all, in any Chromium page/tab/extension.
(it does work in any other software, included VSCode, which has much code in common)
This started happening with a global pkg upgrade in the past 2-3 weeks.
Right now I'm using chromium-79.0.3945.130.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196770

I can use system-wide compose keys with no problem, but in Chromium I can't use the ones I specified in ~/.XCompose.

Upstream issue 351230 seems to have been fixed in Chrome 42, but it isn't to me.

Upstream issue 506838 reports still having problems «running KDE on Debian jessie with Version 47.0.2526.111 (64-bit)».