search

achannarasappa / ticker

Terminal stock ticker with live updates and position tracking
GNU General Public License v3.0
4.94k stars 264 forks source link

segfault #267

Closed herby-popnecker closed 3 months ago

herby-popnecker commented 5 months ago

Describe the bug A clear and concise description of what the bug is.

segmentation fault when launching on rPi 5

To Reproduce Steps to reproduce the behavior:

  1. Downloaded ticker-4.5.14-linux-arm64.tar.gz
  2. tar -xvf ticker.....
  3. chmod +x ticker
  4. sudo mv ticker /usr/local/bin
  5. ./ticker -w IBM

Expected behavior A clear and concise description of what you expected to happen.

Normally, ticker would just launch

Screenshots If applicable, add screenshots to help explain your problem

Additional context Add any other context about the problem here.

herby-popnecker commented 5 months ago

FYI. I am running the same version of ticker on the same O/S on a rPi 4 and it works well --herbie-

thaihugo commented 3 months ago

This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.

To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.

achannarasappa commented 3 months ago

Thanks for reporting the issue and the suggestion on the root cause. I'll take a look into fixing it in the next week or two

herby-popnecker commented 3 months ago

Thank you for taking the time to respond to this problem.Been using ticker for years on rPi. It's regrettable it no longer runs. Do you know if i change the kernel page size in config.txt will result in any performance issues on the rPi5 ? On Thursday, May 30, 2024 at 04:31:02 AM CDT, thaihugo @.***> wrote:

This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.

To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

thaihugo commented 3 months ago

Officially, it would be around 10% performance lost approximately. But from my experience, you can't really fell the difference if you are not maxing a CPU with an heavyweight app or an emulation. For desktop work, you will probably forget the speed from 16k pages kernel after a few minutes.

Le 2 juin 2024 11:47:21 UTC, herby-popnecker @.***> a écrit :

Thank you for taking the time to respond to this problem.Been using ticker for years on rPi. It's regrettable it no longer runs. Do you know if i change the kernel page size in config.txt will result in any performance issues on the rPi5 ? On Thursday, May 30, 2024 at 04:31:02 AM CDT, thaihugo @.***> wrote:

This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.

To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

-- Reply to this email directly or view it on GitHub: https://github.com/achannarasappa/ticker/issues/267#issuecomment-2143815986 You are receiving this because you commented.

Message ID: @.***>

herby-popnecker commented 3 months ago

Good to know.Appreciate the reply.Hopefully, the author will update the app.Sent from my iPadOn Jun 2, 2024, at 8:16 AM, thaihugo @.***> wrote: Officially, it would be around 10% performance lost approximately. But from my experience, you can't really fell the difference if you are not maxing a CPU with an heavyweight app or an emulation. For desktop work, you will probably forget the speed from 16k pages kernel after a few minutes.

Le 2 juin 2024 11:47:21 UTC, herby-popnecker @.***> a écrit :

Thank you for taking the time to respond to this problem.Been using ticker for years on rPi. It's regrettable it no longer runs.

Do you know if i change the kernel page size in config.txt will result in any performance issues on the rPi5 ?

On Thursday, May 30, 2024 at 04:31:02 AM CDT, thaihugo @.***> wrote:

This probably a bug with 16K pages. If you use the kernel=kernel8.img in the /boot/firmware/config.txt (the one that is actually used on the RPI4) it willl work because this is a 4K page kernel. I've tested this solution myself.

To the developer: This bug is related to the ability in newer kernels to work with 16K memory pages. It means that something in your components is probably not happy with this king of configuration. I hope it can shed some light on what's happening.

—

Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you authored the thread.Message ID: @.***>

--

Reply to this email directly or view it on GitHub:

https://github.com/achannarasappa/ticker/issues/267#issuecomment-2143815986

You are receiving this because you commented.

Message ID: @.***>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

achannarasappa commented 3 months ago

I don't have access to a system to replicate confirm the fix / replicate this issue but I believe it is related to upx and this issue. I've upgraded the version of upx before building the latest release v4.6.3 which should fix the issue. When you have a moment, give the latest version a shot and let me know if it fixes the problem.

thaihugo commented 3 months ago

I don't have access to a system to replicate confirm the fix / replicate this issue but I believe it is related to upx and this issue. I've upgraded the version of upx before building the latest release v4.6.3 which should fix the issue. When you have a moment, give the latest version a shot and let me know if it fixes the problem.

The new v4.6.3 indeed solves the problem. The build runs perfectly on a 16K page kernel. Thanks for solving this so fast!

achannarasappa commented 3 months ago

Glad to hear it fixed the issue!