Form has suddenly stopped working

  • IGARP
    Asked on July 15, 2021 at 8:56 AM

    Hello - we have a form that we have used for a couple of years and this morning it's published link brings up the following instead of the form. This form is used daily by our users. How can we correct it? Thanks!


    <--- Last few GCs ---> [4231:0x386b740] 66 ms: Scavenge 3.6 (7.3) -> 3.5 (8.3) MB, 1.2 / 0.0 ms allocation failure [4231:0x386b740] 449 ms: Scavenge 6.0 (9.9) -> 6.2 (12.9) MB, 0.9 / 0.0 ms allocation failure [4231:0x386b740] 500 ms: Scavenge 8.6 (13.4) -> 7.9 (14.9) MB, 2.2 / 0.0 ms allocation failure [4231:0x386b740] 629 ms: Scavenge 10.2 (14.9) -> 9.7 (20.9) MB, 3.3 / 0.0 ms allocation failure <--- JS stacktrace ---> ==== JS stack trace ========================================= Security context: 0x1c963a9a57c1 2: getSubmitURL [0x192fe2a822d1 :3203] [bytecode=0x3e8cbd1f3821 offset=507](this=0x1f918b91e321 ,formID=0x3e8cbd1c59b9 ) 3: createHTMLCode [0x192fe2a822d1 :3253] [bytecode=0x3e8cbd1e92e1 offset=153](this=0x1f918b91e321 ,forFacebook=0x192fe2a822d1 ) 4: arguments adaptor frame... FATAL ERROR: Deoptimizer::EnsureCodeForDeoptimizationEntry 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: v8::internal::Deoptimizer::EnsureCodeForDeoptimizationEntry(v8::internal::Isolate*, v8::internal::Deoptimizer::BailoutType, int) [/bin/node8] 6: v8::internal::Deoptimizer::EnsureCodeForMaxDeoptimizationEntries(v8::internal::Isolate*) [/bin/node8] 7: v8::internal::compiler::PipelineCompilationJob::PrepareJobImpl() [/bin/node8] 8: v8::internal::CompilationJob::PrepareJob() [/bin/node8] 9: 0xd98a2f [/bin/node8] 10: v8::internal::Compiler::CompileOptimized(v8::internal::Handle, v8::internal::ConcurrencyMode) [/bin/node8] 11: v8::internal::Runtime_CompileOptimized_Concurrent(int, v8::internal::Object**, v8::internal::Isolate*) [/bin/node8] 12: 0x26a8093042fd timeout: the monitored command dumped core Aborted

  • igorbojczuk
    Replied on July 15, 2021 at 9:37 AM

    Hi,
    Thank you for reaching out to us, and sincere apologies for the inconvenience you have experienced.
    I have cleared your forms cache, and your form is working correctly.

    This is a very rare occurrence, but just in case, please refer to this guide on how you can clear your forms cache:
    https://www.jotform.com/help/229-how-to-clear-your-form-cache

    Once again, apologies for the inconvenience.

    Best,
    Igor

  • IGARP
    Replied on July 15, 2021 at 9:39 AM

    THANK YOU so much! And I appreciate the link for future reference. Have a great day!