Closed fjebaker closed 2 weeks ago
Hello @fjebaker, Thank you for the issue and trying to use Lightpanda!
About the issue itself, #256 was about setting a specific list of CPU capabilities with -Dcpu=x86_64_v3+aes
instead of using a list generated at build time from the machine itself.
I did that because I had the same kind of issue: my CPU don't have the sha
instruction at the difference of Github's CI servers.
What I can do is to force a -Dcpu=x86_64
[1] for the nightly build.
I think it will improve the CPU support and I hope, fix your use case. The counter part is is less performance on modern CPUs.
IMO it's more important to allow more users to test the browser. If we want improve perf, we still can re-build the browser w/o this option.
I forced a nightly build with the -Dcpu=x86_64
option.
@fjebaker can you try this new version and let-me know if the issue persists?
https://github.com/lightpanda-io/browser/releases/tag/nightly
Thanks!
Hi @krichprollsch thanks for seeing to this so quickly. I tested the new nightly binary and it works perfectly :+1:
Will close the issue as this is now all resolved. Thanks!
Great news! If you have any question or issue, don't hesitate to open another issue or send me directly an email if you prefer (available on my GH's profile). I would love to hear your feedback an know more about your use case.
Hi! First of all this browser is absolutely excellent, thanks for creating and sharing it!
On one of my machines I hit an illegal instruction when trying to run the
nightly
binary:Looking with
gdb
It's specifically the
vzeroupper
instruction. The server I am trying to uselightpanda
on is quite old and small, and the CPU is not very capable (Intel Celeron). It does not haveavx
capabilities, which is why this is failing.I can imagine non-AVX capable CPUs are probably not your target (given https://github.com/lightpanda-io/browser/issues/256), but flagging this just in case they are.
Would you also happen to know how to build the browser without
avx
capabilities? I can't build natively since the machine is too constrained -- the compile takes at least 4 hours (I gave up after 4).