fix: stack overflow in table.concat function#526
Open
thierry-f-78 wants to merge 1 commit intoyuin:masterfrom
Open
fix: stack overflow in table.concat function#526thierry-f-78 wants to merge 1 commit intoyuin:masterfrom
thierry-f-78 wants to merge 1 commit intoyuin:masterfrom
Conversation
tul
reviewed
Mar 12, 2025
tablelib.go
Outdated
| } | ||
| } | ||
| L.Push(stringConcat(L, L.GetTop()-retbottom, L.reg.Top()-1)) | ||
| L.Push(LString(result)) |
Contributor
There was a problem hiding this comment.
Worth considering go lang string builder? https://pkg.go.dev/strings#Builder ?
Author
There was a problem hiding this comment.
Sorry for the late reply, I missed the notification!
Thanks for the suggestion! Indeed, strings.Builder would be more efficient for string construction, especially with large tables. I'll update the code to use strings.Builder instead of simple concatenation.
The previous implementation of tableConcat was pushing all values and
separators onto the Lua stack before concatenating them, which caused
stack overflow with large tables.
This fix changes the implementation to build the result string
incrementally rather than pushing all values onto the stack first,
preventing stack overflow with large tables.
Example that would previously fail but now works correctly:
```
package main
import "github.com/yuin/gopher-lua"
func main() {
var L *lua.LState
var err error
L = lua.NewState()
defer L.Close()
err = L.DoString(`
local t = {}
for i = 1, 10000 do
t[i] = tostring(i)
end
local s = table.concat(t, ',')
`)
if err != nil {
println(err.Error())
}
}
```
affd4e4 to
44ded6a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: Stack Overflow in table.concat Function
This PR fixes a stack overflow issue in the
table.concatfunction when working with large tables.Problem
The previous implementation of
tableConcatpushed all values and separators onto the Lua stack before concatenating them. This approach caused stack overflow errors when dealing with large tables.Solution
This fix changes the implementation to build the result string incrementally rather than pushing all values onto the stack first. Instead of accumulating items on the stack, we now:
Testing
The fix has been verified with large tables that previously caused stack overflow. For example, this test case now works correctly:
This example would previously fail with a stack overflow error but now executes successfully.