[erlang-questions] How to introspect atom table?

[Max Lapshin]

It is a bad idea to increase atom limit, because it will just prolong the
suffering.
1 million of atoms is enough for a simple program.


On Tue, Nov 20, 2012 at 4:05 PM, Zabrane Mickael <zabrane3@REDACTED> wrote:

> Did you try increase this limit:
> $ erl ... +t 4194304
>
> Regards,
> Zabrane
>
> On Nov 20, 2012, at 12:47 PM, Max Lapshin wrote:
>
> Atoms: 1048576
> =memory
> total: 507885448
> processes: 336611825
> processes_used: 336601278
> system: 171273623
> atom: 52749265
> atom_used: 52707589
> binary: 6311816
> code: 3898230
> ets: 2209656
> =hash_table:atom_tab
> size: 411527
> used: 322545
> objs: 1048577
> depth: 21
>
>
> This looks like a problem, yes?
>
>
>
> On Tue, Nov 20, 2012 at 3:10 PM, Gleb Peregud <gleber.p@REDACTED> wrote:
>
>> AFAIK crash dump contains atom list.
>>
>> Also erlang:memory(atom) or erlang:memory(atom_used) can be useful
>>
>> On Tue, Nov 20, 2012 at 12:06 PM, Max Lapshin <max.lapshin@REDACTED>
>> wrote:
>> > Erlang system is crashing with atom limit.
>> > Is it possible to look inside atom table, maybe I'll see something like:
>> > 'user_15', 'user_157' and will quickly find source of problems.
>> >
>> > _______________________________________________
>> > erlang-questions mailing list
>> > erlang-questions@REDACTED
>> > http://erlang.org/mailman/listinfo/erlang-questions
>> >
>>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121120/02cbd48b/attachment.htm>