Narrowing the problem down, on an error the error handler serialises
the current UI state (which can be very large) to EDN and persists that
in a DB. I am thinking something in there is throwing an exception
which, when I try to log it out, causes the recursion. This throws
another exception and
Great tip - thanks Ragnar
On Tue, 27 Sep 2016, at 11:41 AM, Ragnar Dahlén wrote:
> Hi Colin,
>
> I think you're correct in that something is calling print on a largish
> data structure (possibly due to "loops" like Thomas points out), and
> due to the recursive nature of print you're running out
Hi Colin,
I think you're correct in that something is calling print on a largish data
structure (possibly due to "loops" like Thomas points out), and due to the
recursive nature of print you're running out of stack space. The JVM
(hotspot anyway) will by default only keep the top 1024 stack
Thanks Thomas. The NREPL is a red herring as that is a printout from my
local machine - the production error doesn't reference any REPLs - I should
have stated that. Unfortunately I can't get it from production as it is a
very locked down environment (no copy and paste, no internet connection
Hi all,
I have a problem that has been hounding me for a while but has increased in
frequency. Basically, something goes wrong with my code and I get a mother
of all stack traces, but my code isn't referenced in it anywhere.
My gut is telling me it is to do with schema validation - when that
