Re: Emacs launches excruciatingly slowly

[rusi <rustompmody@gmail.com>]

On Nov 3, 10:43 am, Eli Zaretskii <e...@gnu.org> wrote:
> > From: Ryan Wersal <r...@ryanwersal.com>
> > Date: Wed, 2 Nov 2011 14:34:40 -0500
> > Cc: "<help-gnu-em...@gnu.org>" <help-gnu-em...@gnu.org>
>
> > I can confirm that all network drives are functioning correctly. Just to be thorough, I also removed all network drives. The problem continues to persist.
>
> Can you use some OS-monitoring tool, like Process Monitor, to see just
> what Emacs is doing during those long minutes?
>
> If you can install GDB (you can find one on the MinGW site), then
> starting GDB like this:
>
>  gdb -p EMACS_PID
>
> where EMACS_PID is the Emacs process ID (a number shown, e.g., by the
> Task Manager), and then, once GDB is up and shows its "(gdb)" prompt,
> typing this command:
>
>  (gdb) thread apply all bt
>
> will show where each one of the Emacs threads is wasting the time.
>
> Doing that procedure several times during the wait should reveal where
> this time is spent.  (After each "thread apply" command, type "q" to
> exit the debugger and let Emacs run some more, then repeat the above
> recipe.)
>
> (It sounds like this kind of issue should be discussed not here, but
> rather on emacs-de...@gnu.org, or as part of a bug report sent with
> "M-x report-emacs-bug RET" so please follow up there.)

I remember emacs hanging (well maybe I should say 'hanging' because I
did not wait 43 minutes :-).
This must have been about 9-10 years ago, linux box on internal
network when something was wrong with the network.  Dont remember
exactly what wrong...

Doing something to the effect of 'networking off' (again dont remember
the details) made emacs startup normal (2-3 seconds).

Unplugging the network cord without doing the corresponding command
worsens/causes the problem