> Once it happens, you get all kinds of weird stuff -
> duplicate workers with "unique" names, the runtime monitor gets super buggy
> and starts throwing range errors...until you're dead. If you *don't* find
> this result on your gear, please post what version of 4D you're testing
> with.

Yes I have seen this happen, but only for various reasons of my doing like 
killing the worker in the Runtime Explorer without first closing the document. 


> On Oct 8, 2017, at 5:53 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Just try out a compiled version of the original database I sent without any
> of your modifications and let it run for a couple of minutes.

I have done that and it just crashes. My testing has convinced me that the 
crash is the result of the queue reaching it’s limit. Nothing to do with CLOSE 
DOCUMENT.

Try this… Take your copy of the original database and in 
LogWorker_CallABunch_Coop and in LogWorker_CallABunch_Preemptive change $count 
to 200000. That will be 2 million calls to the worker. Do not change anything 
else. For me the test runs without crashing compiled both cooperative and 
preemptive. I have run it several times. It is not a 100 million calls but If 
CLOSE DOCUMENT were in fact an issue I think it would have shown up in 2 
million calls.

As a side note, I am sure you are aware of this, but by killing the worker 
every 100,000 calls, out of the 2 million calls nearly all of the log entries 
are missed as they are in the queue when the worker is killed. I am getting at 
most 24,000 log entries in the text file.

I am running 4D v16 R4 on a MacBook Pro with High Sierra. tested good with 16.2

John


John Baughman
Kailua, Hawaii
(808) 262-0328
john...@hawaii.rr.com





**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to