ng it.
>
> I had this problem…..
>
> David Ringsmuth
>
> From: Chip Scheide via 4D_Tech
> Sent: Friday, October 11, 2019 4:07 PM
> To: Tim Nevels
> Cc: Chip Scheide; 4D iNug Technical
> Subject: Re: stack error - again
>
> On Fri, 11 Oct 2019 15:48:39 -0500,
> On Oct 11, 2019, at 7:08 PM, Dani Beaubien via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> I would suggest contacting 4D Tech Support.
Yes, open the tech case in TAOW or let the support person open it for you.
Milan
**
4D
On Fri, 11 Oct 2019 16:25:55 -0500, Tim Nevels wrote:
> On Oct 11, 2019, at 4:07 PM, Chip Scheide <4d_o...@pghrepository.org> wrote:
>
>> actually its is not compiled component - it is the INTERPRETED version
>> of the component!
>> compile it and it works?!?!?!?!
>
> Thanks for the
On Oct 11, 2019, at 4:07 PM, Chip Scheide <4d_o...@pghrepository.org> wrote:
> actually its is not compiled component - it is the INTERPRETED version
> of the component!
> compile it and it works?!?!?!?!
Thanks for the clarification, I thought this was a compiler issue.
Since it is an
On Fri, 11 Oct 2019 15:48:39 -0500, Tim Nevels wrote:
>
> You said it only happens when you use one specific compiled component
> with one specific host database.
actually its is not compiled component - it is the INTERPRETED version
of the component!
compile it and it works?!?!?!?!
>Why
I do this the opposite way--delete until it ain't broke.
Make a copy and delete half. If it's still broke make a new copy and delete
the other half. If that works, make a new copy and delete half of the
known-broke half. Repeat ten times for 1 in 1024 granularity.
On 10/11/19, 1:29 PM,
Thanks for the ideas - only:
On a Mac.
I have 4 copies of v15
it does not matter which copy I use
Other 4D databases, hosts with components (including the component in
question), and stand alone all function normally.
The data base does not crash.
I get a 4D error, which states (in not exact
On Oct 11, 2019, at 3:21 PM, Chip Scheide wrote:
> and Tim, I may eventually have to do that...build from scratch
> BUT since all of this worked at one point it would be nice to know what
> the root cause of the issue is, so that I (and possibly others) do not
> repeat it.
I know exactly what
On Fri, 11 Oct 2019 14:57:57 -0500, Tim Nevels via 4D_Tech wrote:
> So you know it is a host specific problem. You know what you have to
> do, but you don’t want to do it because it is a PITA and could take
> hours. Start over fresh.
That is just it -
I am not sure it is *just* a host
Again giant PITA, I know, but what other choices do you have?
>
>
if it is a machine specific problem, rebuilding structure may not help.
More useful may be to reinstall system - which is PITA, too.
What may help in such case (and is still PITA) is install Win developer
tools. Then crash should
On Oct 11, 2019, at 2:00 PM, Chip Scheide wrote:
> There is no problem starting the host
> - using a different interpreted component
> - removing all components
>
> The component works with a different host, both interpreted and
> compiled.
So you know it is a host specific problem. You know
The plugin sounds suspect, but you said you removed it... so I'm not sure.
Plugins do have hooks into 4D before startup is run, and they can mess up
memory.
Neil
--
Privacy Disclaimer: This message contains confidential information and is
intended only for the named
lol :)
there are 3 oher threads, 2 here, 1 on the forums.
from memory, and without copy/paste, beside the things listed
previously in this thread
NB: Issue summary (host has 1 component and 1 plugin)
Host started with COMPILED component starts normally
Host started with (specific)
> Anyone have any other ideas?!?!?!?!
Sorry Chip, I have mostly ignored this thread until now... did your run a
maintenance repair on the structure?
I would assume you did, but it wasn't mentioned specifically.
Neil
--
Privacy Disclaimer: This message contains confidential information
I would suggest contacting 4D Tech Support.
Dani
> On Oct 11, 2019, at 10:56 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> In addition to the previous attempts to track this problem down.
> I have recently done the following:
> - examined all forms (both host and component)
In addition to the previous attempts to track this problem down.
I have recently done the following:
- examined all forms (both host and component) for recursive calls to
their respective form methods (which are project methods). - no
recursion found
- insured that all host methods are NOT
16 matches
Mail list logo
