tera_templates bug: thread '<unknown>' has overflowed its stack

[junhwong]

1. Rocket version 0.2.8 ,tera version0.7.2(github current version 0.10)

2. windows 10

3. Includes Lots of TAGS in template，e.g:

<row r="{{lines_count+18}}" spans="1:11" s="5" customFormat="1" x14ac:dyDescent="0.15">
    <c r="D{{lines_count+18}}" s="6"/>
    <c r="E{{lines_count+18}}" s="6"/>
    <c r="F{{lines_count+18}}" s="6"/>
    <c r="G{{lines_count+18}}" s="6"/>
    <c r="H{{lines_count+18}}" s="6"/>
    <c r="I{{lines_count+18}}" s="6"/>
  </row>
  <row r="{{lines_count+19}}" spans="4:9" s="5" customFormat="1" x14ac:dyDescent="0.15">
    <c r="D{{lines_count+19}}" s="6"/>
    <c r="E{{lines_count+19}}" s="6"/>
    <c r="F{{lines_count+19}}" s="6"/>
    <c r="G{{lines_count+19}}" s="6"/>
    <c r="H{{lines_count+19}}" s="6"/>
    <c r="I{{lines_count+19}}" s="6"/>
  </row>
  <row r="{{lines_count+20}}" spans="4:9" s="5" customFormat="1" x14ac:dyDescent="0.15">
    <c r="D{{lines_count+20}}" s="6"/>
    <c r="E{{lines_count+20}}" s="6"/>
    <c r="F{{lines_count+20}}" s="6"/>
    <c r="G{{lines_count+20}}" s="6"/>
    <c r="H{{lines_count+20}}" s="6"/>
    <c r="I{{lines_count+20}}" s="6"/>
  </row>

4. cago run, bug: thread '' has overflowed its stack

[SergioBenitez]

Can you post the full backtrace?

[junhwong]

sry, I do not know how to get backtrace.

[cafeclimber]

RUST_BACKTRACE=1 cargo <build, run, etc>

[junhwong]

I set RUST_BACKTRACE=1 but still the same。

set RUST_BACKTRACE=1
cargo run

[cafeclimber]

I think @SergioBenitez might have meant posting the error in its entirety instead of just the bit saying that the the thread's stack overflowed. Outside of that, I didn't see you were using Win10. If you're in powershell, it looks like you can do

$env:RUST_BACKTRACE = 1

to get the full stack trace.

[junhwong]

@SergioBenitez @cafeclimber i tried set RUST_BACKTRACE=1 It is effectived, but Rocket seems to intercept the error or what is hidden。

[SergioBenitez]

@junhwong Can you copy/paste the full output you're getting in your terminal? Including everything that is logged? You should run the command RUST_BACKTRACE=1 cargo run.

[junhwong]

this test case 1:

...>cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target\debug\poms.exe`
thread 'main' panicked at 'This function never returns!', src\main.rs:115
stack backtrace:
   0: std::sys_common::backtrace::_print
             at C:\projects\rust\src\libstd\sys_common\backtrace.rs:71
   1: std::panicking::default_hook::{{closure}}
             at C:\projects\rust\src\libstd\panicking.rs:354
   2: std::panicking::default_hook
             at C:\projects\rust\src\libstd\panicking.rs:371
   3: std::panicking::rust_panic_with_hook
             at C:\projects\rust\src\libstd\panicking.rs:549
   4: std::panicking::begin_panic<&str>
             at C:\projects\rust\src\libstd\panicking.rs:511
   5: poms::main
             at .\src\main.rs:115
   6: panic_unwind::__rust_maybe_catch_panic
             at C:\projects\rust\src\libpanic_unwind\lib.rs:98
   7: std::rt::lang_start
             at C:\projects\rust\src\libstd\rt.rs:52
   8: main
   9: __scrt_common_main_seh
             at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253
  10: BaseThreadInitThunk
error: process didn't exit successfully: `target\debug\xxx.exe` (exit code: 101)

this case normal(project):

...>cargo run
   Compiling xxx v0.1.0 (file:///...)

    Finished dev [unoptimized + debuginfo] target(s) in 17.72 secs
     Running `target\debug\xxx.exe`
🔧  Configured for development.
    => address: 0.0.0.0
    => port: 3000
    => log: normal
    => workers: 4
🛰  Mounting '/': ...
🚀  Rocket has launched from http://0.0.0.0:3000...
GET /api/produce:
    => Matched: GET /api/produce

thread '<unknown>' has overflowed its stack
error: process didn't exit successfully: `target\debug\xxx.exe` (exit code: 3221225725)

[freinn]

The normal situation when you are getting that error is recursion. Check if you are recursing in your code and try to:

1. get rid of it.
2. use in a way that works.

[SergioBenitez]

@junhwong If you make your template shorter (IE, cut in half or so), does the error go away? If so, this would mean that it's purely a Tera issue.

[junhwong]

@SergioBenitez Yes. it is a Tera bug and report to Keats/tera#185