I doubt very much that it's related to the two processes. It sounds
like you have an error that in some way cripples the rest of the
system. For example, by occuring inside an important critical
section such that something else can't run while the exception
window is open. Or putting something into a state such that when
something else tries to run it also causes an error.
The simplest thing to do would be to run
Notifier current: ErrorNotifier
and when the condition occurs you'll get the error written to an
error.log file and can look at it.
Hi,
I’m moving to VW 7.8
but, despite some nice improvements (_wincall is nice), it
seems unusable.
I had several
incidents when more than on Error notifications come up
(my first naïve theory), the image blocks up completely.
Ctrl-y and Ctrl-Shift-y does not work and the process
manager does not come up (on German keyboard Ctrl-#). I
can still switch between windows and they repaint OK, but
the windows associated with the error(s) and the notifiers
are just blank. The reasons for the errors are presumably
simple (MNU or similar). My guess is that the new split
into two host processes is creating a deadlock when more
than one error occurs.
This makes developing
really difficult (kill process, recover changes and try
again) and is an absolute no-go for the products I want to
deliver.
Any idea how I can get
a handle on that? Would the debug engine be of help here?
Or do I really have to ditch the 7.8 and revert to 7.7.1?
If anybody has an idea
how to narrow the problem down, I’m happy to help.
Cheers,
Christian
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
