https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #121 from Mark Johnston ---
(In reply to jimbo from comment #120)
Is there any reason to think that your problem is related? Do any of the
workarounds listed here help?
If not, a separate PR is warranted. If possible, try to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
ji...@renner.se changed:
What|Removed |Added
CC||ji...@renner.se
--- Comment #120
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #119 from Oliver Fromme ---
(In reply to robert.ayrapetyan from comment #118)
The fix is in stable/11, but not in releng/11.2, as far as I can see.
If you need to have the fix, I suggest updating to 12.0.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
robert.ayrapet...@gmail.com changed:
What|Removed |Added
CC||robert.ayrapet...@gmai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #117 from Carlos J. Puga Medina ---
It was time to close this PR :)
Thanks to all who have contributed to making it possible!
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Carlos J. Puga Medina changed:
What|Removed |Added
Status|Open|Closed
Resolution|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #116 from Rob Belics ---
(In reply to Alexander Zagrebin from comment #114)
Ditto. This works for me, too.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #115 from Nicola Mingotti ---
(In reply to Alexander Zagrebin from comment #114)
I am under FreeBSD 11.1, installed via chromium-68.0.3440.106_1
via pkg.
I tested for two days, your methods works, no hangs.
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Alexander Zagrebin changed:
What|Removed |Added
CC||a...@zagrebin.ru
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #113 from commit-h...@freebsd.org ---
A commit references this bug:
Author: markj
Date: Fri Aug 17 16:04:21 UTC 2018
New revision: 337975
URL: https://svnweb.freebsd.org/changeset/base/337975
Log:
MFC r337328:
Don't check r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #112 from Mark Johnston ---
(In reply to Rob Belics from comment #111)
As noted earlier, the fix hasn't been ported to the 11.x branch yet. I plan to
do that later today, so 11-STABLE users will get the fix soon. I'll see abou
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #111 from Rob Belics ---
(In reply to Sean Chittenden from comment #110)
FreeBSD rob 11.2-RELEASE-p2 FreeBSD 11.2-RELEASE-p2 #0: Tue Aug 14 21:45:40 UTC
2018 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #110 from Sean Chittenden ---
(In reply to Rob Belics from comment #109)
@rob: Can you provide the output of your `uname(1)`, `sysctl kern.osreldate`,
and the version of Chromium in use (`pkg version -n chromium`)?
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #109 from Rob Belics ---
I beg to differ. I find tabs that still hang after surfing the web today. Using
top I see about 20 processes open with three tabs sitting in GMail, Google
Drive and Stack Overflow, with the SO tab being
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Dmitri Goutnik changed:
What|Removed |Added
CC||d...@syrec.org
--- Comment #108 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #107 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cpm
Date: Thu Aug 16 06:57:26 UTC 2018
New revision: 477309
URL: https://svnweb.freebsd.org/changeset/ports/477309
Log:
MFH: r477294
www/chromium:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #106 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cpm
Date: Wed Aug 15 22:54:56 UTC 2018
New revision: 477294
URL: https://svnweb.freebsd.org/changeset/ports/477294
Log:
www/chromium: Update to 68.0.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #105 from Nicola Mingotti ---
(In reply to Oliver Fromme from comment #104)
Hi Oliver, you are right, I apologize.
I am running STABLE, I jumped in moved by comment n.94.
I can't change to CURRENT => I will wait.
bye
n.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #104 from Oliver Fromme ---
(In reply to Nicola Mingotti from comment #103)
Are you running a recent version of -current that includes the fix mentioned in
comment #96? If you don't, please update, or have a little patience unti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #103 from Nicola Mingotti ---
Hi guys,
I am re-trying Chromium, installed by package
-
pkg info | grep chrom
chromium-67.0.3396.87
-
The tabs haging problem seems resolved in general
so chapeaux, you found the w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #102 from Carlos J. Puga Medina ---
*** Bug 226720 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
___
freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Carlos J. Puga Medina changed:
What|Removed |Added
CC||drhowarddrf...@charter.net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #100 from Carlos J. Puga Medina ---
*** Bug 216039 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
___
freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #99 from Carlos J. Puga Medina ---
(In reply to Mark Johnston from comment #98)
Thanks for your work! I'll commit chromium update to 68.0.3440.106 including
the new information in the pkg-message.
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #98 from Mark Johnston ---
Thanks for the feedback. I had set a fairly long MFC timeout period on the
change but will aim to merge in the next several days instead, given the
relative severity of the bug and the lack of fallout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #97 from bk...@cs.ucl.ac.uk ---
(In reply to Sean Chittenden from comment #96)
The prospect of the elimination of this bug is fantastic news--after 23 years,
I was starting to reluctantly consider giving up on FreeBSD for deskto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Sean Chittenden changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #9
Grzegorz Junka writes:
> On 20/07/2018 19:28, bugzilla-nore...@freebsd.org wrote:
>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
>>
>> --- Comment #81 from Jan Beich ---
>> Can someone check if the patch in bug 181741 has any effect? Maybe some hangs
>> (e.g., cache on high latenc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #95 from Scott Hazen Mueller ---
Well, I solved my own problem: After some 25 years, I no longer run FreeBSD as
a desktop. Chrome is plenty stable on Mac.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #94 from tim...@gmail.com ---
I can't any problems on chromium-67.0.3396.87 anymore.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-chromium@fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #93 from Sean Chittenden ---
Use of an md(4) FS to replace ~/.cache/chromium may have reduced the rate of
hung tabs for some people, but it certainly hasn't made any material impact
from my perspective. Because of that, I wish
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #92 from Rob Belics ---
This failed quickly with hanging tabs just a couple of hours after trying it.
--
You are receiving this mail because:
You are the assignee for the bug.
___
fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #91 from Rob Belics ---
(In reply to Carlos J. Puga Medina from comment #90)
Entering this manually did work. GMail tab, the first thing I opened, did seem
to hang but I only waited 20 seconds. I will use chromium for the rest o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #90 from Carlos J. Puga Medina ---
Just follow the instructions of www/chromium/pkg-message
# mkdir /home/user/.cache/chromium
Add this line to your /etc/fstab
md /home/user/.cache/chromium mfs rw,late,-wuser:group,-s300m 2 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #89 from Carlos J. Puga Medina ---
(In reply to Rob Belics from comment #88)
Hey, next time I will not answer your question(s)
You can do it manually.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #88 from Rob Belics ---
(In reply to Carlos J. Puga Medina from comment #87)
Don't ask silly questions.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #87 from Carlos J. Puga Medina ---
(In reply to Rob Belics from comment #86)
Have you replace 'joe' with your username?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #86 from Rob Belics ---
(In reply to Carlos J. Puga Medina from comment #84)
mount ~{joe}/.cache/chromium
mount: ~{joe}/.cache/chromium: unknown special file or file system
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #85 from Oliver Fromme ---
(In reply to isuy from comment #82)
That error occurs if you use csh / tcsh. The commands from comment #65 use
POSIX shell syntax and work with bash, zsh or FreeBSD's /bin/sh.
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #84 from Carlos J. Puga Medina ---
(In reply to isuy from comment #82)
Please, read the following message posted on freebsd-chromium ML
https://lists.freebsd.org/pipermail/freebsd-chromium/2018-July/003608.html
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #83 from Rob Belics ---
(In reply to isuy from comment #82)
I thought I was doing something wrong, and maybe I am, but I have this same
issue.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
i...@socal.rr.com changed:
What|Removed |Added
CC||i...@socal.rr.com
--- Comment #
On 20/07/2018 19:28, bugzilla-nore...@freebsd.org wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #81 from Jan Beich ---
Can someone check if the patch in bug 181741 has any effect? Maybe some hangs
(e.g., cache on high latency storage but not GPU driver bugs) are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #81 from Jan Beich ---
Can someone check if the patch in bug 181741 has any effect? Maybe some hangs
(e.g., cache on high latency storage but not GPU driver bugs) are due to IPC.
Just a wild guess.
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #80 from Tomo ---
The "--disk-cache-size=0" command line option was effective for me.
It improved problem of freezing during rendering(but not completely).
I'm also using following workarounds(I don't know if it's all necessary
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Scott Hazen Mueller changed:
What|Removed |Added
CC||sc...@zorch.sf-bay.org
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Bart Ender changed:
What|Removed |Added
CC||hs.sp...@gmail.com
--- Comment #78 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #77 from Carlos J. Puga Medina ---
(In reply to Nicola Mingotti from comment #74)
Of course, it does not solve the problem but it shows that the current problem
is not specific to FreeBSD.
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #76 from Nicola Mingotti ---
In the first 4 hours of today Chromium was working
significantly better than usual, far less page hanging.
The only difference respect to a normal day is that today
I did not still run Google Docum
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #75 from Nicola Mingotti ---
(In reply to Thomas Zander from comment #72)
I agree with you Thomas, also to me changing
to memory disk had not significant effect.
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #74 from Nicola Mingotti ---
(In reply to Carlos J. Puga Medina from comment #73)
Hi Carlos, I never used "ulimit" before but I guess
it will not be the solution.
If i type "ulimit" in my system I get:
"unlimited"
BTW, I do
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #73 from Carlos J. Puga Medina ---
(In reply to Thomas Zander from comment #72)
OpenBSD was affected by this issue. They proposed the following workaround:
"Your default datasize might not be enough for v8 so if you experience
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #72 from Thomas Zander ---
(In reply to Yuri Victorovich from comment #65)
The memory backed cache does not help at all. For me, the experience stays
exactly the same: If the system has no load, chromium works usually fine, oft
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #71 from Yuri Victorovich ---
(In reply to Oliver Fromme from comment #70)
Chrome's bug site has tens of thousands of open reports, so it's unlikely to
help.
IMO, it should be reported on their subreddit: https://www.reddit.co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #70 from Oliver Fromme ---
(In reply to Grzegorz Junka from comment #62)
No, the same issue occurs with Chrome on Linux and Windows for some people.
It's not FreeBSD-specific. There are quite a lot of threads on various websites
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #69 from Nicola Mingotti ---
(In reply to Yuri Victorovich from comment #68)
That command does not work out of the box, i get
---
Skipped '/usr/ports'
svn: E155007: None of the targets are working copies
---
Probably some time
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #68 from Yuri Victorovich ---
(In reply to Nicola Mingotti from comment #67)
You need to 'svn update'.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #67 from Nicola Mingotti ---
(In reply to Yuri Victorovich from comment #65)
Thank you for Yuri, in my /usr/ports/www/chromium/pkg-message
there is only this:
-
For correct operation, shared memory sup
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #66 from Yuri Victorovich ---
(In reply to Nicola Mingotti from comment #64)
It puts the cache directory on the memory disk.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #65 from Yuri Victorovich ---
(In reply to Nicola Mingotti from comment #64)
www/chromium/pkg-message has this explanation:
# [ -d ~{user}/.cache/chromium ] || mkdir ~{user}/.cache/chromium
# echo "md $(echo ~{user})/.cache/chr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #64 from Nicola Mingotti ---
(In reply to Yuri Victorovich from comment #57)
Youri could you explain more in detail what you did ?
"Tomo Method" worked well on my system but still I have
big issues with WhatsApp Web, I would
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Wayne Sierke changed:
What|Removed |Added
CC||w...@au.dyndns.ws
--- Comment #63 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #62 from Grzegorz Junka ---
(In reply to Oliver Fromme from comment #58)
Chrome works fine on Linux and Windows. What makes you think it's a problem
that needs to be fixed in Chrome (by Chrome developers) and not a problem with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #61 from Nicola Mingotti ---
To my browser "Tomo Procedure" made miracles !
I forwarded the wisdom to the Forum.
In run
-] FreeBSD-11.1 in a VMWare virtual machine, MacBook host, OSX 10.11.6
-] GPU disabled with "--disable-gpu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #60 from Nicola Mingotti ---
I ask my self, why do we call the binary "chrome" if this
is actually "chromium" ? Also the package name is "chromium".
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #59 from Yuri Victorovich ---
(In reply to Oliver Fromme from comment #58)
> I'm afraid there's nothing FreeBSD can do about it. This needs to be fixed by
> the Chromium devs.
Chrome is structured the way that they only suppo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Oliver Fromme changed:
What|Removed |Added
CC||o...@freebsd.org
--- Comment #58 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #57 from Yuri Victorovich ---
(In reply to timp87 from comment #56)
Using memory-fs for ~/.cache/chromium solved the problem completely for me on
11amd64, chromium-64.0.3282.186.
--
You are receiving this mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #56 from tim...@gmail.com ---
(In reply to Dmitri Goutnik from comment #55)
This WA does completely no difference to my hanging chromium at least on my
home 12-CURRENT with AMD video card. Just like '"Simple Cache for HTTP"
feat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Bug 212812 depends on bug 226793, which changed state.
Bug 226793 Summary: www/chromium: Workaround description for the hanging tabs
problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226793
What|Removed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Yuri Victorovich changed:
What|Removed |Added
Depends on||226793
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Dmitri Goutnik changed:
What|Removed |Added
CC||d...@syrec.org
--- Comment #55 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #54 from Grzegorz Junka ---
(In reply to Carlos J. Puga Medina from comment #53)
How is it going to help with crashing or hanging on FreeBSD?
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #53 from Carlos J. Puga Medina ---
I recommend to enable the "Simple Cache for HTTP" feature.
This is a new caching backend for Chrome which aims to reduce the amount of
time it takes to re-validate cached files in your browser
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #52 from Atsushi Hasumoto ---
I used FreeBSD 11.1 Release.
I found fix bug chromium browser.
My machine is nvidia graphics card.
so, upgrade nvidia driver is fix bug.
driver version is latest.
I wonder if would be helpful.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #51 from Thomas Zander ---
(In reply to Rob Belics from comment #49)
The messages about GetIdleWakeupsPerSecond() not being implemented should not
be a problem (fingers crossed, though). Chromium continuously samples metrics
of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Nicola Mingotti changed:
What|Removed |Added
CC||nmingo...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #49 from Rob Belics ---
If this is helpful, here is the output on my terminal:
[1091:530669568:0228/170558.730061:ERROR:gl_context_glx.cc(232)] Couldn't make
context current with X drawable.
[1091:530669568:0228/170558.730099:E
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #48 from Rob Belics ---
(In reply to Carlos J. Puga Medina from comment #46)
What I found throughout today was that I no longer see tabs crashing, as
another bug report shows, but I do see tabs hanging. In every case, I was abl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #47 from Grzegorz Junka ---
For me an easy way to reproducing this issue is to go to youtube.com and keep
opening new videos from recommendations in new tabs. Every few tabs opened
there will be a tab that hangs loading the vide
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #46 from Carlos J. Puga Medina ---
(In reply to Rob Belics from comment #43)
I'm not sure if it would help in your case but I'm using the OpenGL ES 2.0
SwiftShader.
Just disable the GPU hardware acceleration to use SwiftShader
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #45 from bourne.ident...@hotmail.com
---
Ah yes. I see it now easily - and the last time I looked hard and failed to
spot it. Thanks a lot, CPM.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #44 from Carlos J. Puga Medina ---
(In reply to bourne.ident...@hotmail.com from comment #40)
From the menu it's: top-right Chromium Menu/three vertical dots (⋮) > More
tools > Extensions.
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #43 from Rob Belics ---
(In reply to Carlos J. Puga Medina from comment #37)
I tried those values and one tabs crashed almost immediately. However, since
then, chromium seems to be running well.
That said, I've noticed two th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #42 from tim...@gmail.com ---
(In reply to Carlos J. Puga Medina from comment #41)
Sure. In my workload it hardly matters.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #41 from Carlos J. Puga Medina ---
(In reply to timp87 from comment #39)
The kern.maxfiles sysctl variable should change according to the workload of
your machine, the number of services running concurrently, etc.
These are no
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
bourne.ident...@hotmail.com changed:
What|Removed |Added
CC||bourne.ident...@hotma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
w.schwarzenf...@utanet.at changed:
What|Removed |Added
See Also||https://bugs.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #39 from tim...@gmail.com ---
(In reply to Carlos J. Puga Medina from comment #37)
I've just tried these parameters on my FreeBSD 11.1-RELEASE amd64 workstation.
Nothing changed, chromium tabs hang as before.
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Grzegorz Junka changed:
What|Removed |Added
CC||li...@gjunka.com
--- Comment #38
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #37 from Carlos J. Puga Medina ---
(In reply to timp87 from comment #36)
chromium works fine on 10.3/amd64, I didn't notice the tabs hanging issue since
I bumped up the maximum number of open files via sysctl.conf(5)
kern.maxf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #36 from tim...@gmail.com ---
Unfortunately, chromium is now almost totally unusable with 63.0.3239.132
version :(
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #35 from Thomas Zander ---
There must be some timing / locking related component to this problem.
On my desktop (11/stable, sandybridge w/ integrated graphics) these hangs can
easily triggered just by firing load onto the CPUs.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Rob Belics changed:
What|Removed |Added
CC||robbel...@gmail.com
--- Comment #34 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
--- Comment #33 from Vince Mulhollon
---
Problem seems to be getting worse over the last few months and last few
upgrades, to the point I've had to switch to Firefox recently now that tab
rendering success rate is well below 10%.
With no
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
s...@efers.org changed:
What|Removed |Added
CC||s...@efers.org
--- Comment #32 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Carlos J. Puga Medina changed:
What|Removed |Added
URL||https://bugs.chromium.org/p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Vladimir Krstulja changed:
What|Removed |Added
Status|New |Open
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Atsushi Hasumoto changed:
What|Removed |Added
CC||a.hasum...@gmail.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Domagoj Stolfa changed:
What|Removed |Added
CC||domagoj.sto...@gmail.com
--- Comm
1 - 100 of 131 matches
Mail list logo
