[ImageJ-bugs] [Bug 933] Fiji very slow boot up

[bugzilla at fiji.sc]

http://fiji.sc/bugzilla/show_bug.cgi?id=933

--- Comment #12 from Leon Yang <leonyang1994 at gmail.com> ---
(In reply to Leon Yang from comment #11)
> (In reply to Leon Yang from comment #10)
> > (In reply to amc910 from comment #9)
> > > Hi there,
> > > 
> > > I've come over from Bug 1170.
> > > 
> > > I'm having problems taking a stack trace. Pressing Ctrl+Pause/Break just
> > > seems to give me the command line back again, with no other output.
> > > 
> > > Any suggestions?
> > > 
> > > Kind regards,
> > > Angus
> > 
> > Hi,
> > 
> > For some reason, the Ctrl+Pause/Break is not working right now. We will
> > check what's the problem later.
> > 
> > Alternatively what you can try, is to find the pid of the running Fiji 
> > (using "ps ax | grep ImageJ" in the console, and the first number appears
> > should be the pid). Then enter "jstack -F <pid_of_imagej>", and that should
> > return you the stack dump.
> > 
> > Hopefully that can help,
> > 
> > Leon
> 
> If you are using Windows, you can either enter the next line:
> tasklist /fi "imagejname eq ImageJ-win64.exe"
> in the console (you should change the executable name on the previous line
> the match the one you are using),
> 
> or go to the task manager->Processes tab->right click the bar on the top,
> which has "Name" "CPU" "Memory" etc.->select the PID menu item->go to the
> ImageJ app and look for its pid.
> 
> Please reply if there is anything unclear.
> 
> Leon

The command to get the pid should be this one instead:
tasklist /fi "imagename eq ImageJ-win64.exe"
Sorry for the confusion.

Leon

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-bugs/attachments/20151019/2e25f70c/attachment.html>