| |
| |
On 1/29/23 21:29 Albrecht Schlosser wrote:
I can't find anything useful in these logs which I'm attaching. In
both logs 'fluid' is started, once by running `fluid/fluid` (relative
path: this hangs) and the other by `/tmp/fltk/fluid/fluid` (full path:
works). Maybe someone else can see what's happening or can test on
their system(s). Mine is macOS Ventura 13.1 on MacBook Air (M1).
The names of the logs are self-explanatory, and as far as I can see
they are very similar until the "hanging" fluid stops. Notable
difference: the "working" process issues "SetFrontProcess: asn=
options=1" somewhat later than the hanging process - and continues to
work and logs more messages.
Maybe someone else can find the underlying issue and maybe even find a
workaround?
Maybe it *has* to do with the hidden "/private" in the working
directory and app directory before "/tmp"?
Here's a new observation: there seems to be some kind of deadlock, or
our process waits for something to happen.
I did the following:
(1) execute fluid/fluid - hangs
(2) close notebook lid (suspends macOS ?)
(3) open notebook lid - yeah, the fluid window is there and works!!
As I said, maybe some kind of deadlock that's resolved by a system
message that "awakes" the fluid process?
See attached and commented log. This is something for someone more
familiar with macOS, maybe Manolo?
To make clear what I did, here's a summary from memory:
1. create git worktree or clone a fresh FLTK source tree in /tmp/fltk
(or another dir under /tmp)
2. cd to /tmp/fltk
3. make [-j7]
4. launch `fluid/fluid` - this hangs
5. suspend macOS (closing the notebook lid) - or maybe something else?
6. open the notebook: the window appears and is responsive
I also tried `cd /private/tmp/fltk` but - although `pwd` reports it
correctly - it doesn't change anything.
I remember that I backgrounded the running and hanging fluid process by
typing 'ctrl/z'. Some time later I foregrounded the process ('fg') and
the window appeared. However, I could not reproduce this when I tried
again. I can't tell what happened while the fluid process was
backgrounded and waiting. Maybe I had closed the notebook meanwhile, but
that's only a guess, I can't remember.
Manolo, is this of any help to find what's causing the window to not
appear when a process is launched
(a) under /tmp
(b) from the shell with a *relative* path
(c) from a bare binary, not inside a bundle
Using the full path to run fluid or running the binary from the bundle,
or copying it somewhere else, all this seems to "heal" the effect.
Really weird!
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/08830632-2151-dfed-7772-79d134ddc939%40online.de.
default 22:13:17.778337+0100 fluid Received configuration update from daemon (initial)
default 22:13:17.781559+0100 fluid CHECKIN: pid=90812
default 22:13:17.784049+0100 fluid CHECKEDIN: pid=90812 asn=0x0-0x3ff8ff5 foreground=0
default 22:13:17.788763+0100 fluid FRONTLOGGING: version 1
default 22:13:17.788798+0100 fluid Registered, pid=90812 ASN=0x0,0x3ff8ff5
default 22:13:17.790745+0100 fluid Current system appearance, (HLTB: 1), (SLS: 0)
default 22:13:17.791701+0100 fluid No persisted cache on this platform.
default 22:13:17.792679+0100 fluid Current system appearance, (HLTB: 1), (SLS: 0)
default 22:13:17.793087+0100 fluid Post-registration system appearance: (HLTB: 1)
default 22:13:17.802226+0100 fluid SetFrontProcess: asn=0x0-0x3ff8ff5 options=1
default 22:13:17.803137+0100 fluid Registering for test daemon availability notify post.
default 22:13:17.803248+0100 fluid notify_get_state check indicated test daemon not ready.
default 22:13:17.803371+0100 fluid notify_get_state check indicated test daemon not ready.
default 22:13:17.803494+0100 fluid notify_get_state check indicated test daemon not ready.
default 22:13:17.805811+0100 fluid SignalReady: pid=90812 asn=0x0-0x3ff8ff5
default 22:13:17.806335+0100 fluid SIGNAL: pid=90812 asn=0x0x-0x3ff8ff5
--- process hangs, closing notebook lid ---
--- opening notebook again ---
default 22:13:28.845009+0100 fluid SetFrontProcess: asn=0x0-0x3ff8ff5 options=1
default 22:13:28.897110+0100 fluid NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x6000037e7b80
(
"<NSAquaAppearance: 0x6000037e7d80>",
"<NSSystemAppearance: 0x6000037e7080>"
)>
default 22:13:28.962630+0100 fluid order window front conditionally: 44a related: 0
--- process works ---
default 22:13:44.608043+0100 fluid order window front conditionally: 44a related: 0
default 22:13:49.988375+0100 fluid order window front conditionally: 44d related: 0
default 22:13:50.014364+0100 fluid order window: 44d op: 0 relative: 0 related: 0
default 22:13:51.164601+0100 fluid Entering exit handler.
default 22:13:51.164643+0100 fluid Sending exit barrier. activeSendTransactions=0
default 22:13:51.164794+0100 fluid Exiting exit handler.
[ Direct Link to Message ] | |
|
| |
