Mon, May 22 2006
12:15:29
|
|
Request created by guest
|
|
Subject: v.hull, nviz: the GUI window freezes
Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 2006-05-18
When v.hull (or nviz points=) is called from TCL/TK GUI it spits so many
WARNING: Attributes for category XXX not found
that the window freezes.
I realise this is because "Adapted sites library used for vector points (module
should be updated to GRASS 6 vector library)" but many users will not understand
it (eg. those who never heard of Grass 5) and for them it makes v.hull and nviz
look like it fails/freezes when a big number of point is in the input (on my
machine about 400 points is enough to experience this).
Maciek
|
|
Tue, May 23 2006
00:12:22
|
|
Mail sent by mneteler
|
|
hi,
the warning is issued in
lib/sites/sites.c
The solution is to update v.hull to GRASS 6 (so, to
not used the outdated sites lib).
Markus |
|
Tue, May 23 2006
00:12:40
|
|
Comments added by mneteler
|
|
... same applies to NVIZ of course... |
|
Tue, May 23 2006
16:40:43
|
|
Mail sent by msieczka
|
|
Markus wrote:
> The solution is to update v.hull to GRASS 6 (so, to
> not used the outdated sites lib).
It would be great, for v.hull and NVIZ, but it is not nature of the problem
now I see.
I have just noticed that any command in GUI that outputs quite long text at a
high pace, will freeze the window temporarily. It's wish occupies 100% CPU
then and only "kill -9" is able to close it. If you leave it alone, it will
complete though. Yet for many users it will look like a freeze, when it takes
eg. a minute for the command to complete and the window completely doesn't
respond during that time. Especially that the completion takes noticably
longer in GUI than in the terminal, for some reason.
Try "r.stats -1 some_raster" in GUI for instance.
Renaming the bug to: "TCLTK GUI: window freezes with a long text output at
high pace", as this issue is not limited to nviz or v.hull only.
Interestingly, the r.stats ouptput in GUI was *longer* than in console, see:
$ r.stats -1 hipso_nn | wc -l
r.stats: 100%
610878
while after copy/paste from r.stats GUI output into Gedit I had 610899 lines
of output, hmm.
Maciek
|
|
Tue, May 23 2006
16:43:29
|
|
Subject changed to TCLTK GUI: command window freezes due to a very verbose text output by msieczka
|
|
Fri, Jul 7 2006
16:58:31
|
|
Owner changed to cshock by mneteler
|
|
Fri, Jul 7 2006
16:58:31
|
|
Mail sent by mneteler
|
|
Hi,
still an issue? Maybe Cedric has a comment?
Markus |
|
Fri, Jul 7 2006
21:55:14
|
|
Mail sent by msieczka
|
|
On Fri, 7 Jul 2006 16:58:31 +0200 (CEST)
Markus Neteler via RT <grass-bugs@intevation.de> wrote:
> still an issue? Maybe Cedric has a comment?
Yup, still alive and kicking in current CVS. Several hundreds of lines printed
are able to freeze TCL/TK window of r.stats (nviz, v.hull, other) for the
command run-time.
Maciek
|
|
Fri, Jul 7 2006
21:55:32
|
|
Mail sent by msieczka
|
|
On Fri, 7 Jul 2006 16:58:31 +0200 (CEST)
Markus Neteler via RT <grass-bugs@intevation.de> wrote:
> still an issue? Maybe Cedric has a comment?
Yup, still alive and kicking in current CVS. Several hundreds of lines printed
are able to freeze TCL/TK window of r.stats (nviz, v.hull, other) for the
command run-time.
Maciek
|
|
Wed, Jul 26 2006
18:43:12
|
|
User changed to tutey@o2.pl by msieczka
|
|
Sat, Jun 9 2007
23:22:29
|
|
Mail sent by msieczka
|
|
Hi
Letting you know that this bug is still there. I have just experienced it with
v.distance.
Some modules prone to this bug (in general - any module which might print few
hundred lines or more quite quickly):
v.hull
nviz
v.distance
r.stats
db.select
v.db.select
v.report
v.to.db
When the bug crops out, it looks like if the given module freezed: 100% CPU
usage, module's tcl/tk window does not refresh. For real the command still
works, but it gets several times slower than if run from the terminal, which
adds to the impression that the module has freezed.
The bug is present in current 6.2 and 6.3 CVS. Using tcl/tk 8.4.12 at build
time and run time. Ubuntu Dapper 32bit, kernel 2.6.15. As well as on 2 other
machines, of which one is 64bit.
It's quite a widespread and important problem for tcl/tk GUI users. Can we do
anything about it?
Maciek
|
|