IDE instability on Raspberry Pi?

[ron.dunn]

Any other IDE users on Pi out there?

I've found the IDE to be rock-solid on Intel Linux Mint, but I'm not having the same experience on Pi. Random hangs and crashes, once taking the editor file with it.

The Pi only has Raspbian (64 bit headless) and Free Pascal on it, accessed via Mint's Gnome terminal.

Curious if others have faced a similar problem.

[Thaddy]

I have no problems on any Raspberry pi (1 to 5) but on 3 and lower and just 1MB memory it is advised to increase the swap space a bit (usually as much swap space as you have physical memory)
And don't over do the amount of components installed, but that is also an issue on Intel.

The only problems I have is burning SD carts... Better to configure an external SSD.

My surviving RPi 1 is 512 Mb, My RPi 5 's are 4Gb

[ron.dunn]

Thank you, Thaddy.

This is an 8Gb Pi5, and boots from an SSD. It is reassuring you don't have a problem. I have more than one Pi, so I'll swap with another and see what happens.

[Thaddy]

Note I have had some problems running a 8G RPi5 (not mine, I have only some 4GB) under 32 bit. On AARCH64 it works just fine.
But those problems are very likely not related to yours.

[TRon]

fwiw for me 64-bit bookworm on a pi4 8g is very unstable even after changing from wayland to x. No matter which software. I am considering to revert back to bulls-eye.

[ron.dunn]

I'm not using the GUI, TRon, just Raspbian Lite. Console all the way It's why I'm loving Free Pascal, the text mode IDE has taken me back 40 years, to a better time of programming.

I have a few doing different jobs, they're all solid, with the exception of the new environment I put together for Free Pascal.

Anyway, let's see what happens after I switch to another Pi, with a fresh install of OS and Pascal.

[TRon]

I'm not using the GUI, TRon, just Raspbian Lite.

Drats, my bad. Indeed you wrote headless.

Anyway, let's see what happens after I switch to another Pi, with a fresh install of OS and Pascal.

I you can be bothered then let us know if that fixed things for you or not.

[ron.dunn]

There's definitely an issue here. Different Pi, fresh OS, fresh Free Pascal; and the IDE hangs if it is left idle for an extended period of time. It seems to be around 20-30 minutes.

Tried a couple of other editors - Nano, MCEdit - neither has shown the problem.

I also don't see the problem if I'm running on an Intel Linux install, using the same terminal. It seems to be Pi-specific.

[af0815]

There's definitely an issue here. Different Pi, fresh OS, fresh Free Pascal; and the IDE hangs if it is left idle for an extended period of time. It seems to be around 20-30 minutes.

Have you tired to start from a terminal and activated logging (https://wiki.freepascal.org/LazLogger), yes lazarus is normal build with logging. So it is possible to see what it is doing for this log time.

[ron.dunn]

I don't use Lazarus, is it something that can be done from the IDE?

[ccrause]

Have you tired to start from a terminal and activated logging (https://wiki.freepascal.org/LazLogger), yes lazarus is normal build with logging. So it is possible to see what it is doing for this log time.

I don't use Lazarus, is it something that can be done from the IDE?

No, LazLogger is Lazarus specific.

[Thaddy]

I don't use Lazarus, is it something that can be done from the IDE?

The IDE is usually interpreted as Lazarus, not the textmode IDE where you are referring to.
AARCH64 is quite a new architecture for the pi, so it may well be that there are some issues with fp, the textmode ide.

[rvk]

I can confirm some problems with ./fpc/bin/fp text ide on RPI4 bookworm.

I can access all the menu options, except File. When activating or selecting the File mainmenu option, the IDE freezes.
Also... when opening menu, options and help, after escaping out of that window, the window itself stays on screen (as ghost image).

I'll try on a RPI3 bookworm later on.

[rvk]

On rpi3 with bookworm 64bit it also hangs on File menu.
With rpi3 with bullseye 32bit it works but the screen handling is still a mess via SSH.

[ron.dunn]

Thank you rvk, it's good to know I'm not the only one