Tailboard Report - Unfillable

  • UCCLLC
    Asked on June 29, 2021 at 8:31 AM

    Our morning tailboard is unviewable when clicked to complete. We get the information below:

    <--- Last few GCs ---> [1795:0x23c2740] 2669 ms: Mark-sweep 38.4 (53.4) -> 31.0 (49.8) MB, 18.2 / 0.0 ms (+ 65.8 ms in 92 steps since start of marking, biggest step 8.3 ms, walltime since start of marking 940 ms) finalize incremental marking via stack guard GC in old space[1795:0x23c2740] 3463 ms: Scavenge 45.9 (57.5) -> 41.1 (60.5) MB, 10.0 / 0.0 ms allocation failure [1795:0x23c2740] 4466 ms: Scavenge 61.2 (72.7) -> 57.6 (91.2) MB, 29.4 / 0.0 ms allocation failure <--- JS stacktrace ---> Cannot get stack trace in GC. FATAL ERROR: NewSpace::Rebalance Allocation failed - process out of memory 1: node::Abort() [/bin/node8] 2: 0x11e7fec [/bin/node8] 3: v8::Utils::ReportOOMFailure(char const*, bool) [/bin/node8] 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/bin/node8] 5: 0xad2f0b [/bin/node8] 6: v8::internal::MarkCompactCollector::Evacuate() [/bin/node8] 7: v8::internal::MarkCompactCollector::CollectGarbage() [/bin/node8] 8: v8::internal::Heap::MarkCompact() [/bin/node8] 9: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/bin/node8] 10: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/bin/node8] 11: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/bin/node8] 12: v8::internal::String::SlowFlatten(v8::internal::Handle, v8::internal::PretenureFlag) [/bin/node8] 13: v8::internal::parsing::ParseProgram(v8::internal::ParseInfo*, v8::internal::Isolate*) [/bin/node8] 14: 0xd999db [/bin/node8] 15: v8::internal::Compiler::GetSharedFunctionInfoForScript(v8::internal::Handle, v8::internal::Handle, int, int, v8::ScriptOriginOptions, v8::internal::Handle, v8::internal::Handle, v8::Extension*, v8::internal::ScriptData**, v8::ScriptCompiler::CompileOptions, v8::internal::NativesFlag) [/bin/node8] 16: v8::ScriptCompiler::CompileUnboundInternal(v8::Isolate*, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions) [/bin/node8] 17: v8::ScriptCompiler::CompileUnboundScript(v8::Isolate*, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions) [/bin/node8] 18: 0x121b49e [/bin/node8] 19: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo const&)) [/bin/node8] 20: 0xb7aecf [/bin/node8] 21: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [/bin/node8] 22: 0x223b374842fd timeout: the monitored command dumped core Aborted

  • Jovanne JotForm Support
    Replied on June 29, 2021 at 11:12 AM

    Hi, thank you for contacting support.

    Could you please give us more details about your concern so we can assist you properly?

    Are you perhaps referring to this form https://www.jotform.com/form/200694907695064?

    I have checked the form and its submission data, and they seem to be working fine on my end.

    Could you please try clearing your browser cache or try it on a different device and check if the issue persists?

    We look forward to your response.

  • UCCLLC
    Replied on June 29, 2021 at 12:38 PM

    Our employees are trying to complete that form. Every single one of them (all using different devices) are getting the same error as do I -


    This is the error:

    <--- Last few GCs ---> [1795:0x23c2740] 2669 ms: Mark-sweep 38.4 (53.4) -> 31.0 (49.8) MB, 18.2 / 0.0 ms (+ 65.8 ms in 92 steps since start of marking, biggest step 8.3 ms, walltime since start of marking 940 ms) finalize incremental marking via stack guard GC in old space[1795:0x23c2740] 3463 ms: Scavenge 45.9 (57.5) -> 41.1 (60.5) MB, 10.0 / 0.0 ms allocation failure [1795:0x23c2740] 4466 ms: Scavenge 61.2 (72.7) -> 57.6 (91.2) MB, 29.4 / 0.0 ms allocation failure <--- JS stacktrace ---> Cannot get stack trace in GC. FATAL ERROR: NewSpace::Rebalance Allocation failed - process out of memory 1: node::Abort() [/bin/node8] 2: 0x11e7fec [/bin/node8] 3: v8::Utils::ReportOOMFailure(char const*, bool) [/bin/node8] 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/bin/node8] 5: 0xad2f0b [/bin/node8] 6: v8::internal::MarkCompactCollector::Evacuate() [/bin/node8] 7: v8::internal::MarkCompactCollector::CollectGarbage() [/bin/node8] 8: v8::internal::Heap::MarkCompact() [/bin/node8] 9: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/bin/node8] 10: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/bin/node8] 11: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/bin/node8] 12: v8::internal::String::SlowFlatten(v8::internal::Handle, v8::internal::PretenureFlag) [/bin/node8] 13: v8::internal::parsing::ParseProgram(v8::internal::ParseInfo*, v8::internal::Isolate*) [/bin/node8] 14: 0xd999db [/bin/node8] 15: v8::internal::Compiler::GetSharedFunctionInfoForScript(v8::internal::Handle, v8::internal::Handle, int, int, v8::ScriptOriginOptions, v8::internal::Handle, v8::internal::Handle, v8::Extension*, v8::internal::ScriptData**, v8::ScriptCompiler::CompileOptions, v8::internal::NativesFlag) [/bin/node8] 16: v8::ScriptCompiler::CompileUnboundInternal(v8::Isolate*, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions) [/bin/node8] 17: v8::ScriptCompiler::CompileUnboundScript(v8::Isolate*, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions) [/bin/node8] 18: 0x121b49e [/bin/node8] 19: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo const&)) [/bin/node8] 20: 0xb7aecf [/bin/node8] 21: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [/bin/node8] 22: 0x223b374842fd timeout: the monitored command dumped core Aborted

  • Jovanne JotForm Support
    Replied on June 29, 2021 at 5:48 PM

    Hi,

    Could you please share with us a screenshot of the error you see on your end?

    GUIDE: how-to-post-screenshots-to-our-support-forum

    Is the form embedded on a site? If so, could you also please share the site URL so we can check?

    Can we also send a test submission to the form so we can try to replicate the issue?

    We look forward to your response.