Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2022-04

Lazarus is running but not responding.

10 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael Van Canneyt

Hi,

Lazarus was completely stuck under high load.

No way to close it. I had to kill Lazarus with

killall -KILL lazarus

When I then attempted to restart lazarus, I got
"Lazarus is running but not responding."
(see screenshot)

I have not found a way to start it again.

So, what should I do now ?

Michael.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: running.png
Type: image/png
Size: 7765 bytes
Desc:
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20220421/3d4d005b/attachment.png>

Reply by email

Ondrej Pokorny
to Michael Van Canneyt: Lazarus was completely stuck under high load. No way to close it. I had to kill Lazarus…
Michael Van Canneyt wrote 13 lines
Lazarus was completely stuck under high load. No way to close it. I had to kill Lazarus with killall -KILL lazarus When I then attempted to restart lazarus, I got "Lazarus is running but not responding." (see screenshot) I have not found a way to start it again. So, what should I do now ?

It means that the IPC files are still blocked. Please restart your PC and write back if it didn't help.

This Lazarus part is something I am not really proud of and should be rewritten...

Ondrej

Reply by email

Michael Van Canneyt
to Ondrej Pokorny: It means that the IPC files are still blocked. Please restart your PC and write back if…
Ondrej Pokorny wrote 17 lines
On 21.04.2022 11:36, Michael Van Canneyt via lazarus wrote: > Lazarus was completely stuck under high load. > > No way to close it. I had to kill Lazarus with > > killall -KILL lazarus > > When I then attempted to restart lazarus, I got "Lazarus is running but not > responding." > (see screenshot) > > I have not found a way to start it again. > > So, what should I do now ? It means that the IPC files are still blocked. Please restart your PC and write back if it didn't help.

Restarting the PC is NOT an option at this point, and won't be for the next couple of hours...

Where are these files located ?

Michael.

Reply by email

Michael Van Canneyt
to Michael Van Canneyt
Michael Van Canneyt wrote 26 lines
On Thu, 21 Apr 2022, Ondrej Pokorny via lazarus wrote: > On 21.04.2022 11:36, Michael Van Canneyt via lazarus wrote: >> Lazarus was completely stuck under high load. >> >> No way to close it. I had to kill Lazarus with >> >> killall -KILL lazarus >> >> When I then attempted to restart lazarus, I got "Lazarus is running but >> not responding." >> (see screenshot) >> >> I have not found a way to start it again. >> >> So, what should I do now ? > > It means that the IPC files are still blocked. Please restart your PC and > write back if it didn't help. Restarting the PC is NOT an option at this point, and won't be for the next couple of hours... Where are these files located ?

OK. Found it, they are in /tmp/*LazarusMain*

Well, this is definitely something that can be improved :-)

Michael.

Reply by email

Ondrej Pokorny
to Michael Van Canneyt
Michael Van Canneyt wrote 10 lines
On Thu, 21 Apr 2022, Michael Van Canneyt via lazarus wrote: > Restarting the PC is NOT an option at this point, and won't be for > the next > couple of hours... > > Where are these files located ? OK. Found it, they are in /tmp/*LazarusMain* Well, this is definitely something that can be improved :-)

Yes, definitely. I will note it down again. It bugs me as well.

Ondrej

Reply by email

Martin Frb
to Ondrej Pokorny: It means that the IPC files are still blocked. Please restart your PC and write back if…
Ondrej Pokorny wrote 6 lines
It means that the IPC files are still blocked. Please restart your PC and write back if it didn't help. This Lazarus part is something I am not really proud of and should be rewritten...

It's also very annoying, if you have a hanging IDE instance. It is impossible to start a 2nd instance to attach and debug.

Even if you don't wont any of it: The most "permissive" setting is "always start a new instance".
And even though, this should never need to know (nor be known) if another instance is running, it initializes the IPC stuff (and hangs, if ...).

Maybe it was meant, if an instance from a diff installation (with diff config) has a setting that says to "use a running instance". But even then, it is imho incorrect, to use an instance that says, it does not want to be used.
That is to me, if I have a config "always start a new instance", then that means both:
- do not look for a running instance, if started with files to open:?? lazarus? unitfoo.pas
- do not get found/used for opening additional files, when a lazarus with different config checks for a running instance. ? (because this running instance says, the files should go into a new instance. So this running instance can not be hijacked to open files)

--------------------
Anyway, in git main branch I added a new command line param. (I added it because fppkg gave me huge time outs. And also some of the other warnings, which I know I can ignore in my development folder.) The option can be added in the lazarus.cfg file. From there it will be read even if you start the IDE from a desktop shortcut.

For the unique-instance / ipc it is
?? --skip-checks=SingleInstance

Other values are:
--skip-checks=LazarusDir,FpcExe,FpcSrc,Make,Debugger,Fppkg,Setup,MissingPackageFile,InstallDir,SingleInstance,MacroScript,All

*** WARNING:
*** Disabling those checks means you will not be warned about any issues. *** Related functionality may be broken, and you are on your own to find out why...

For the initial setup dialog (those checks normally run on every start, to check if the dialog should be shown)
??? LazarusDir,???????? // Correct Lazarus-dir /
CheckLazarusDirectoryQuality
??? FpcExe,???????? // fpc.exe / CheckFPCExeQuality ??? FpcSrc,???????? // fpc source dir / CheckFPCSrcDirQuality ??? Make,?????????? // make.exe / CheckMakeExeQuality ??? Debugger,?????? // CheckDebuggerQuality
??? Fppkg,????????? // CheckFppkgConfiguration
??? Setup,????????? // **All** of the above

??? MissingPackageFile, // lisPkgSysPackageFileNotFound = 'Package file not found';
??? InstallDir,???? // This Config was last used by this/other installation ??? SingleInstance, // Other running IDE // Attempt to get lock file ??? MacroScript, // Package EditorMacroScript, skip self test

??? All???????????? // **ALL**

Reply by email

Ondrej Pokorny
to Mattias Gaertner
Mattias Gaertner wrote 7 lines
On Fri, 22 Apr 2022 14:47:14 +0200 Martin Frb via lazarus wrote: > [...] > It's also very annoying, if you have a hanging IDE instance. It is > impossible to start a 2nd instance to attach and debug. lazarus.exe --force-new-instance

Yes, it is annoying. I'll improve it.

Ondrej

Reply by email