"Returning an object but pool is full" spammed in Transcript

[kiran-kp]

I'm very new to smalltalk/pharo/gtoolkit and am having trouble diagnosing this issue. I have a fresh download of gtoolkit v0.8.2253 for Linux. As soon as I open gtoolkit and open Transcript the log message Returning an object but pool is full is spammed repeatedly. It makes it impossible to use Transcript because this does not stop and clearing the window does not help.

Happy to provide more information if someone can give me tips to investigate.

OS: Fedroa 37
RAM: 16GB
Display: Wayland

[girba]

Thank you for the issue. It is not your fault :). This issue comes from the underlying Pharo library for threaded FFI. We will look into it.

In the meantime, what are you trying to add to Transcript? An alternative can be Beacon. Please take a look in the Glamorous Toolkit book.

[kiran-kp]

I wasn't actually trying to do anything with Transcript. I just noticed some performance issues and went poking around when I noticed the log spam. Feel free to close this issue if it's a duplicate.

[nergal-perm]

As a workaround I can suggest finding all the occurencies of 'pool is full' strings and commenting out all found lines of code. Searching is done like that:

'pool is full' gtSubstringMatch

Or you can go straight away to class TFPool and check its method returnOne: - that's the spamming thing.

I always do that for a fresh GT image.

[girba]

@nergal-perm thanks for letting us know that you do that all the time :).

But my question is: do you need to open the Transcript often?

[nergal-perm]

Oh, I don't use Transcript at all :) but the thing is that image grows in size every time I save it. I suppose it's because of those log messages. Clearing the Transcript helps, but it's temporary.

[girba]

Hmm, those log messages should not affect much the image size.