chromium issue

A big thank you to @cpm and the Chromium team for all the work on this web-bowser. For now I will just
use Firefox and Firefox-esr, both are working on my i386 architectures.

I suspect there may be special files and/or directories that are needed to be in place for Chromium to work correctly. As I always create a very minimalist system, this style of system building is prone to many unorthodox maladies. Nevertheless, I learn alot from these adventures, and I have a whole lot of fun doing so!

Furthermore, monwarez discussed building a system in a clean environment (so that dependencies either missing, incompatible, or wholesale wrong) are not pulled into the system.
 
FWIW, the patch earlier in this thread improves Chromium usability, which is good.
But, even if Chromium now get "hung" tabs less often, they are still there. As before, the only way is to close that tab. When the frequency of this problem increases, I just stop and start Chromium.
 
bookwormep said:
A big thank you to @cpm and the Chromium team for all the work on this web-bowser. For now I will just
use Firefox and Firefox-esr, both are working on my i386 architectures.

I suspect there may be special files and/or directories that are needed to be in place for Chromium to work correctly. As I always create a very minimalist system, this style of system building is prone to many unorthodox maladies. Nevertheless, I learn alot from these adventures, and I have a whole lot of fun doing so!

Furthermore, monwarez discussed building a system in a clean environment (so that dependencies either missing, incompatible, or wholesale wrong) are not pulled into the system.
Click to expand...

I have in mind to update chromium and iridium to the latest stable release (TBD). To solve the segfault on i386, first I need to fix the DEBUG option to get a reliable stack trace and see what's wrong here.
 
cpm@ said:
I have in mind to update chromium and iridium to the latest stable release (TBD). To solve the segfault on i386, first I need to fix the DEBUG option to get a reliable stack trace and see what's wrong here.
Click to expand...

Hi,

I'm newbie, but I get to compile the latest chromium 61 version in DEBUG adding manually the /usr/local/lib/libfontconfig.so to the solibs key in gfx.ninja.
Unfortunally, I try to launch chromium inside gdb and I get only the memory address where the segmentation occurs without information about the code.
Please, could you help me?
 
I know this is not a real "issue", but I'd like to ask you guys:
What do you think are the chances of getting the Linux pepper flash plugin working on FreeBSD chromium?

(The plugin can be extracted from a Linux chrome executable and, at least theoretically installed into FreeBSD Chromium.
I did that a while ago. But I was unable to get it working. Maybe I made a bad manifest file or other issues prevented the Flash to activate.)
 
Okay, installed chromium v. 61.0.3160.100 as a package; then, launched but still Seg. Fault.
However, I read the revision r.457431 and it detailed a switch to: llvm50; while, I have the
older llvm40-4.0.1_1. Also, next time around I should probably set Debug and Test options.
 
bookwormep said:
Okay, installed chromium v. 61.0.3160.100 as a package; then, launched but still Seg. Fault.
However, I read the revision r.457431 and it detailed a switch to: llvm50; while, I have the
older llvm40-4.0.1_1. Also, next time around I should probably set Debug and Test options.
Click to expand...

Packages are built weekly from a snapshot of the ports, therefore, you need to install it from ports if you don't want to wait.

In addition, chromium was tested on 10.3/i386 and 11.1/i386. See PR 224622 for further details.
 
Snurg said:
I know this is not a real "issue", but I'd like to ask you guys:
What do you think are the chances of getting the Linux pepper flash plugin working on FreeBSD chromium?

(The plugin can be extracted from a Linux chrome executable and, at least theoretically installed into FreeBSD Chromium.
I did that a while ago. But I was unable to get it working. Maybe I made a bad manifest file or other issues prevented the Flash to activate.)
Click to expand...

Chromium no longer support Flash and was deprecated due to security concerns.

https://www.chromium.org/flash-roadmap
 
Vincenzo Isaia said:
Hi,

I'm newbie, but I get to compile the latest chromium 61 version in DEBUG adding manually the /usr/local/lib/libfontconfig.so to the solibs key in gfx.ninja.
Unfortunally, I try to launch chromium inside gdb and I get only the memory address where the segmentation occurs without information about the code.
Please, could you help me?
Click to expand...

Please, file a new PR via bugzilla.
 
Okay, I will give it another try. If I try to build from ports it takes over 18 hours, I don't want to melt cpu, sorry.

Edit: I will write back by the end of today, otherwise: Thanks for all the help on this!
 
bookwormep said:
I'm glad you mentioned fans, as it was, I positioned a household fan right up to the side of the Thinkpad and kept it running for most of the time.
Click to expand...

I had to do the same thing with my old Gateway Solo laptop or it would shut itself down as a safety measure.

I noticed a syslog warning in one of my terminals just last week while compiling ports on a T61 and saw it had reached 100C. I hooked up the gaming fan and brought it down to a safe level in no time. I need to take it apart and look at it because that's not normal.
 
You must log in or register to reply here.
Back
Top