Just checked where the bazel cache physically is and it is:

/private/var/tmp/_bazel_zsolt

most likely I'm having the same issue as the one you are discussing.

> (1) execute fluid/fluid - hangs
> (2) close notebook lid (suspends macOS ?)
> (3) open notebook lid - yeah, the fluid window is there and works!!

I played with this and it did work! Not exactly my desired dev
workflow though :)

On Sun, Jan 29, 2023 at 1:39 PM Albrecht Schlosser
<AlbrechtS.fltk@online.de> wrote:
>
> 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 a topic in the Google Groups "fltk.general" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/fltkgeneral/miGhgA3y0xE/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

-- 
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/CADaF38QhjBi-PQujoofxBna301_-LHHh-ioKhQCpciPtF1o%3DYw%40mail.gmail.com.