Shmeekz Posted April 26, 2015 Posted April 26, 2015 Cant paste the actual debug logs but I have the screenshots. http://puu.sh/hr5DR/95b4b6280f.jpg part 2http://puu.sh/hr5c0/2813583b6c.jpg
Precise Posted April 26, 2015 Posted April 26, 2015 Cant paste the actual debug logs but I have the screenshots. http://puu.sh/hr5DR/95b4b6280f.jpg part 2 http://puu.sh/hr5c0/2813583b6c.jpg Does this ever happen when you're not out of memory? because i can see you're maxed out on memory for the client. i would recommend assigning more memory to the client so this won't occur as frequently ^_^. If this still occurs when not full memory then im not too sure. An error is occurring in the onExit() of Czar's script which might be an error on either his side or the client but we won't know as the client doesn't show where the bug is.
Shmeekz Posted April 26, 2015 Author Posted April 26, 2015 Oh I see, I will make sure to allocate mor memory
Botre Posted April 26, 2015 Posted April 26, 2015 If this still occurs when not full memory then im not too sure. An error is occurring in the onExit() of Czar's script which might be an error on either his side or the client but we won't know as the client doesn't show where the bug is. Sigh. Weren't they going to add stacktraces for onStart() and onExit()? Inb4alektellsustowrapitinatrycatch 1
Botre Posted April 26, 2015 Posted April 26, 2015 Sigh. Inb4itellyouthattheyalreadyare self-sigh, my bad :x
