Firestorm Master branch

[Drakeo]

I noticed this commit today.

Linux; Disable GPU once more, as once again having it on causes issues on some systems.

https://vcs.firestormviewer.org/phoenix-firestorm/changeset/cef73bce8f2469ee7ec9fc95970831be0e1a0ccc

 	mPickedFiles.clear();
 	mCurVolume = 0.0;
+#ifdef LL_LINUX
+	mDisableGPU = true;
+#endif
+	
 	mCEFLib = new dullahan();
 	setVolume();

Right now this saddens me. I am unable to reproduce these problems. I rather like having the use of my GPU for rendering media on webpages.

This isn't a put down  but a regression do to hardware and compliance.  Is this a gamer program or not. Do you think Chrome or Chromium turn this off by default.

So right now the FS team is building for older I mean way older CPU's That isn't as big of a deal.  If the Firestorm users like me at times  is being held back because people want to run hardware that isn't  up to the programs standards.  NickyD  why not have two builds.  At some point like me people will need to upgrade the hardware.

But if your running a intel graphics like an i7 APU and  the Linux users are penalized  why not give the people the choice. Not that hard to rebuild the media plugin.

Just a thought.

I use the internal browser for all links.

 

 

Edited September 18, 2021 by Drakeo

[Drakeo]

Think about striping your cef3-bin  binaries before packing them or stripping them when building Dullahan. I mean your not building a debug build of CEF3 not really going to help you when using debug option when starting FS.

283 mb  as a tarball and 1.2 gigs extracted. wow. 

[Beq Janus]

Then back out the change locally. 

You are choosing to build from a live development branch not from the last release branch, as such you are exposed to all kinds of daily churn, you also have the freedom to ignore any updates you don't think you need.

[mygoditsfullofstars]

Its disabled because its broken in the current CEF release for some reason.

@DrakeoFeel free to compile and debug CEF and let me know what the issue is. This was making my logs about 2GB in size in no time.

 

Edited September 19, 2021 by mygoditsfullofstars

[MarissaOrloff]

I have an i7-9750H and a RTX-2080 and had the issues from the photo above. I don't think that qualifies as "old" Drakeo.

Edited September 22, 2021 by MarissaOrloff

[mygoditsfullofstars]

Yep, another team member ended up with a 99GB CEF log and it filled their partition...

So its off for now, we can probably revisit turning GPU acceleration back on next time there's a CEF update for Linux

 

Edited September 22, 2021 by mygoditsfullofstars

[Drakeo]

Is what it is.  not good not bad. just broken dullahan  hey SL no longer supports Linux I see that is catching on. post a log wow.

Time to say The program is broken because you are unable to watch twitch ?

I am sure NickyD understands this tsk

In 3 years they will be porting everything to ARM's cpu Linux. psst only a fool would count out  Google.

to bad for Mac users the platform gives  has issues with  mac's latest rules.

You can see it in the commits.  I build my own  version. now go  gather your debug on CEF.

Edited September 25, 2021 by Drakeo

[Drakeo]

On 9/21/2021 at 9:49 PM, mygoditsfullofstars said:

Yep, another team member ended up with a 99GB CEF log and it filled their partition...

look tell you how lost people are.  Not going to talk windows  platform  only a spoon fed humane in the ISA world would get lost doing that.

Stupidity happens. I build the FS code all three platforms  one a week. OK. S0 I am unable to reproduce using my build. 

If it was  you and I  would see it in the commits .

Only ignorance of the program would lead to this.

Only a smart percentage pushes stable even when your working on the masters edge.

As far as your 99 gig.  LOL  you need to look at the simple log and see that you have an issue. not the software

 LL tested that dullahan over and over . I submitted my builds so they could see it on the bitbucket. UNABLE TO REPRODUCE

This discussion is about  GPU  and dullahan. KISS works.

FS team will fix it. because they  got on the new simplified wagon. Up to FS to push 519.

OK. get to work FS.  Mine works it uses LL code.

Where do you see me disabling  this in The LL  Linux viewer I maintain.

Not good or bad for you.  I want GPU acceleration  when rendering  the platform. Remember we all do not using  a pie menu.

Or legacy sever for profiles that should be taken down do to the SL experience is changed in a huge way. This is SL not FS.

You want to be part of the community NickyD then get your profiles in order.

Other wise we see ruth looking profiles from 2009  in https://my.secondlife.com/

That's where the platform went with hundreds of fine things. Your   legacy path  just ruins marketing and the experience of the client.

Yes you can see your old ugly profile in web option. That is a joke and ruins the SL experience for  me and many others.

Ok See you all next week. right click your back  click a circle click again click again.  tsk.

World class.

Some time you have to find 2021 not 2009.

 

Edited September 25, 2021 by Drakeo

[Drakeo]

On 9/19/2021 at 7:01 AM, mygoditsfullofstars said:

Its disabled because its broken in the current CEF release for some reason.

@DrakeoFeel free to compile and debug CEF and let me know what the issue is. This was making my logs about 2GB in size in no time.

 

Son you  have an issue your working in VM stop being a foolish one. Install it on the hard ware only do not test in virtual machine. If you do not know why. Then please stay away if your a dev.

As you know I post my CEF3 builds and the scripts to build them ok.

I am sure in 2015 I enlightened your team lead what to look for.  And the same in 2017 and in 2013 when I was starting on CEF b4 CEF 3

and The FS team was brilliant in helping with the scripts and pushing  the need Lib's . for old  xorg stuff.

fact is . For me to compile it in Linux.  So all can use it took many days weeks and years to customize a Linux system in the old GLIBC and old GCC 5.5.0 

So it can use vulkan and xwayland etc. I built a tool nothing more nothing less.  and Virtualbox will break some libraries do to the cpu ID issue.

VM machine will break pthread .

 Same reason why Chrome can run on  old Redhat and run on new Redhat. Tools.  Same reason why Mozilla Firefox runs on a 7 year old systems

nothing hidden here https://bitbucket.org/Drakeo/build-cef/downloads/

built in GCC 5.50 here is the script I use.

https://bitbucket.org/Drakeo/slackware64-14-2-cef/src/master/

future script build for the next 3  to 5 years.

https://bitbucket.org/Drakeo/slackware64-15-0-cef/src/master/

 

 

 

Edited September 25, 2021 by Drakeo

[mygoditsfullofstars]

@Drakeo

I am running the viewer on bare metal with the proprietary NVIDIA drivers. Stop making stupid assumptions. Go and look up who I am on the FS website (I'm not some clown who is just experimenting in a VM). I know better than to try and run it in a VM FFS. There is something inherently broken in this release of CEF and GPU acceleration on Linux. I am not the only one who saw the same GPU log error spam. Are you going to accuse the others of trying to run it on a VM too?

Oh and before you even consider saying my hardware is old. Don't go there. Intel i9, RTX-3070 GPU.

 

 

 

Edited September 25, 2021 by mygoditsfullofstars

[Alwin Alcott]

2 hours ago, mygoditsfullofstars said:

Go and look up who I am on the FS website (I'm not some clown who is just experimenting in a VM).
End of discussion.

If you'r sooo important for FS i'd suggest you change your attitude here, explain what is wrong is also possible without insulting the questioner, even when he/sh is wrong.

(and yes.. that comes from me)

Edited September 25, 2021 by Alwin Alcott

[mygoditsfullofstars]

28 minutes ago, Alwin Alcott said:

If you'r sooo important for FS i'd suggest you change your attitude here, explain what is wrong is also possible without insulting the questioner, even when he/sh is wrong.

(and yes.. that comes from me)

I believe he was trying to insult my intelligence by saying I am running it in a VM and the issue must be on my system (go and look at what he wrote and the tone). And he did the same thing when I mentioned that another team member had the same issue (it must be their system too and not an issue with CEF). I treat people how they treat me. Why should I change my attitude when he was the one being condescending and insulting to begin with?

As for my role within the team, I was pointing this out to him so he can learn that he's not dealing with a noob who knows nothing (which is how he was treating me).

Edited September 25, 2021 by mygoditsfullofstars

[mygoditsfullofstars]

<redacted>

Edited September 25, 2021 by mygoditsfullofstars

[mygoditsfullofstars]

I've made an interesting discovery tonight about the log spam in question when GPU acceleration was enabled for CEF (and no, its nothing to do with my system or gpu type or drivers), I am discussing my findings internally with our devs to see what they think. If what I think is the issue turns out to be true I'll post back.

The log spam errors are EGL related.. Why CEF was trying to use EGL on a Linux system is what I am curious about...

 

Edited September 25, 2021 by mygoditsfullofstars

[mygoditsfullofstars]

So it turns out that a subsequent commit to the source after disabling GPU acceleration has unintentionally squelched the log spam (which from my testing seems to be caused if the bundled CEF GL-ES library is loaded), but there is still an underlying issue because CEF is falling back to using swiftshader which is a software renderer (CPU based).

From the CEF source:

Quote

// Select which implementation of GL the GPU process should use. Options are:
// desktop: whatever desktop OpenGL the user has installed (Linux and Mac // default).
// egl: whatever EGL / GLES2 the user has installed (Windows default - actually // ANGLE).
// swiftshader: The SwiftShader software renderer.

It is controllable via the --use-gl flag - but its unclear why CEF has fallen back to swiftshader or why it is trying to use the EGL back-end to begin with - so what I said earlier still stands, this could still be a bug within CEF on linux itself, professor google also suggests that its not the first time CEF has had such issues on Linux. Anyway, if I discover anything else I'll post.

Edited September 26, 2021 by mygoditsfullofstars

[mygoditsfullofstars]

This should be now fixed in https://vcs.firestormviewer.org/phoenix-firestorm/changeset/abd5f7a8993d777fa19e1c2fcd70d2af038e3730

Looks good for me now:

[Nicky Dasmijn]

@Drakeo thank you for your report, I too had problems to reproduce that log spam on my machines. With the current changes, as mygoditsfullofstars wrote, the GPU is on again and I hope no one is getting that amount of spam.

[Drakeo]

Hey NickyD what ever your doing something right  look at the donations  love your work on the lab. I rarely take any one serious in here your  just a cool peep up north unless you moved again.

This issues is the Linux viewer  i love poking at FS pie menu it is my fun thing to do.

SDL DirectFB is the huge bridge to cross I can careless about  dullahan  actually.

SDL2 will build with DirectFB  here the issue. 2014  was the last updates ?

We will have to start linking to the  xorg. ? Xwayland ??? Wayaland .

I see that Linden labs in the DRTVWR-543-maint is slowly removing the code.

This will come back to haunt them when  everyone is building on Arms CPU's. 

I started a build system for the DRTVWR-543 that should build in all Linux systems that are older . This will be moved up as the systems move forward.

And again thank the world Class viewer team Firestorm for all the help they have given to Linden labs.

With out the libraries  for Linux we will be left behind.  If I was you NickyD!  And may be to late your Mole hill has become Mountain.

See you all next week

 

Edited October 2, 2021 by Drakeo

[Drakeo]

On 9/25/2021 at 1:02 AM, mygoditsfullofstars said:

@Drakeo

I am running the viewer on bare metal with the proprietary NVIDIA drivers. Stop making stupid assumptions. Go and look up who I am on the FS website (I'm not some clown who is just experimenting in a VM). I know better than to try and run it in a VM FFS. There is something inherently broken in this release of CEF and GPU acceleration on Linux. I am not the only one who saw the same GPU log error spam. Are you going to accuse the others of trying to run it on a VM too?

Oh and before you even consider saying my hardware is old. Don't go there. Intel i9, RTX-3070 GPU.

 

 

 

run it from here. https://vcs.firestormviewer.org/phoenix-firestorm/commits

Then post a jira OK build it then post it.  WTF is bare metal ?

Edited October 2, 2021 by Drakeo

[Drakeo]

On 9/25/2021 at 4:55 AM, mygoditsfullofstars said:

The log spam errors are EGL related

You have no clue why it is there or you would never post it.  LLError has nothing to do with LL_WARNS it is a tool the spam is good  and is needed.

It goes to /dev/null so wtf. in linux. Windows people. 

Fact is spam is not spam it is the feed back from the the code.  Create the log see where the spam you wanted to make  the log.

Everything you see in  console is what was written the code for you to see.  I am just  having fun. Fact is you have no clue how  "printf" works.

Hey thanks for the cool pics.

[mygoditsfullofstars]

@Drakeo Bare metal means to run it natively on hardware. No virtualization. I am not going to argue with you anymore because I am tired of you being condescending and hostile (and making ill informed assumptions), the point being is that it was broken and trying to use EGL which is not the preferred method on Linux and that was the underlying reason for the log spammage. CEF creates its own log file (cef_log.txt) and also echos that junk out to it, which is the file that was getting massive on the systems of numerous people (so, no, the CEF spam is not just going to STDOUT).

FYI -- I have a programming background in x86 assembler and C and other languages up my sleeve.

Fact is, you make DUMB assumptions. Another fun fact I am a Linux (and Unix) sysadmin with over 20 years commercial experience in the field with Devops up my sleeve. So before you go calling me a windows person and me not knowing what the printf() function is ponder the above for the moment. I've not used windows in many years.

I am done here.

 

 

 

Edited October 3, 2021 by mygoditsfullofstars

[Drakeo]

21 hours ago, mygoditsfullofstars said:

@Drakeo Bare metal means to run it natively

Wow your smart any other slang you want to teach me.  should I  solder another  evergreen 486 into my board or use  a boot strap I am a huge fan so  . Not here to be rude and you are rude and the fact is I am  a huge FS fan. Going to fork it just like Emerald call it  call it Phoenix . Fact is I am a huge fan. so get off me.

I probably will fork it because LL will not add de render to  objects and allow harassment.

Next time you think some one owns something on the GPL you should learn what a boot strap is bare metal man.

Last people rude enough to fork it I had to fix there  builds for them in Inworldz they had no clue. Plock what ever  lol stripped mono from it  omg.

No one cared when the Aurora project happen.  just fork that to.  stop being mean mygoditsfullofstars

Love coming in here.

Quote

FYI -- I have a programming background in x86 assembler and C and other languages up my sleeve.

 look put you work on the bucket give me the link or  be nice.  I been herding this blob for over a decade.  Use my tools or   put your link to your work here.  GPL right.

Edited October 4, 2021 by Drakeo

[Drakeo]

21 hours ago, mygoditsfullofstars said:

FYI -- I have a programming background in x86 assembler and C and other languages up my sleeve.

Number 9 was the last UNIX I dealt with. hey but  Maw Bell was my account.  Instead of being rude we could be talking about  trying to get time on the main frame then

1978 babe all we had was cards and TAR so be nice. Put the links to your work here so we all can be come part of it FS does.

[Drakeo]

By the way I am creating a new build tool that  could help many people you can find it here.  every prebuilt may need a different  variable for per GLBC  GCC you want to contribute that would be nice.

https://bitbucket.org/Drakeo/prebuilt-lib/src/master/

May be time for third party devs to get together on this  it will save a so much time.

Feel free to fork and  send pull request.  After I get Linux done will work on the Mac stuff then Windows stuff.

Be nice if we had a central place to go to it would be nice. .  fork it  create a branch edit your logs.

 

Edited October 4, 2021 by Drakeo