Author Topic: ULib Stack Overflow  (Read 1531 times)

0 Members and 1 Guest are viewing this topic.

Offline Cobalt

  • Full Member
  • ***
  • Posts: 216
  • Karma: 44
  • http://steamcommunity.com/id/__yvl/
ULib Stack Overflow
« on: July 27, 2014, 04:07:15 PM »
Console is getting spammed with this, was there a patch and I'm not updated (3.62 svn 209) or is this a new bug?
Code: [Select]
Lua Error: [ERROR] stack overflow 1. isstring - [C]:-1
2. fn - addons/ulib/lua/ulib/shared/hook.lua:182
3. fn - addons/ulib/lua/ulib/shared/hook.lua:183
4. fn - addons/ulib/lua/ulib/shared/hook.lua:183
5. fn - addons/ulib/lua/ulib/shared/hook.lua:183
6. fn - addons/ulib/lua/ulib/shared/hook.lua:183
7. fn - addons/ulib/lua/ulib/shared/hook.lua:183
8. fn - addons/ulib/lua/ulib/shared/hook.lua:183
9. fn - addons/ulib/lua/ulib/shared/hook.lua:183
10. fn - addons/ulib/lua/ulib/shared/hook.lua:183
11. fn - addons/ulib/lua/ulib/shared/hook.lua:183
12. fn - addons/ulib/lua/ulib/shared/hook.lua:183
13. fn - addons/ulib/lua/ulib/shared/hook.lua:183
14. fn - addons/ulib/lua/ulib/shared/hook.lua:183
15. fn - addons/ulib/lua/ulib/shared/hook.lua:183
16. fn - addons/ulib/lua/ulib/shared/hook.lua:183

Offline Stickly Man!

  • Ulysses Team Member
  • Hero Member
  • *****
  • Posts: 1270
  • Karma: 164
  • What even IS software anymore?
    • XGUI
Re: ULib Stack Overflow
« Reply #1 on: July 28, 2014, 11:09:39 AM »
This is the first I've seen anything like this. It would appear you have an addon of some kind that has a hook that calls itself, resulting in an infinite loop. Are there any addons that have recently changed?
Join our Team Ulysses community discord! https://discord.gg/gR4Uye6

Offline Cobalt

  • Full Member
  • ***
  • Posts: 216
  • Karma: 44
  • http://steamcommunity.com/id/__yvl/
Re: ULib Stack Overflow
« Reply #2 on: July 28, 2014, 02:03:10 PM »
This is the first I've seen anything like this. It would appear you have an addon of some kind that has a hook that calls itself, resulting in an infinite loop. Are there any addons that have recently changed?
As a matter of fact I just found the problem. I was using gamemode.Call to call a hook, while inside another hook of the same type.