Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

メモリ容量の認識がおかしい #3409

Closed
AyaMorisawa opened this issue Nov 26, 2018 · 18 comments
Closed

メモリ容量の認識がおかしい #3409

AyaMorisawa opened this issue Nov 26, 2018 · 18 comments
Assignees
@acid-chicken
Labels
🐛Bug Unexpected behavior

Comments

@AyaMorisawa
Copy link
Contributor

AyaMorisawa commented Nov 26, 2018 •
edited
Loading

Summary
@AyaMorisawa
Copy link
Contributor Author

AyaMorisawa commented Nov 26, 2018 •
edited
Loading

ターミナルで

export LC_ALL=C; free -b ; unset LC_ALL

と入力すると、

             total       used       free     shared    buffers     cached
Mem:   1676422348815827468288  936755200   11292672  620691456 8835600384
-/+ buffers/cache: 637117644810393047040
Swap:   1022357504     196608 1022160896

と表示される。

@AyaMorisawa
Copy link
Contributor Author

AyaMorisawa commented Nov 26, 2018 •
edited
Loading

ターミナルで

free -g

と入力すると、

             total       used       free     shared    buffers     cached
Mem:            15         14          1          0          0          8
-/+ buffers/cache:          5          9
Swap:            0          0          0

と表示される。

@AyaMorisawa
Copy link
Contributor Author

原因はsysteminformationパッケージであることが判明。

https://github.com/sebhildebrandt/systeminformation/blob/2bf55c48df5fed8aa351c3b5c6d9278c127b8dd1/lib/memory.js#L116-L117

free -b の結果の total と used の値が隣接しているケースが考慮されていない。

@AyaMorisawa AyaMorisawa added the 🐛Bug Unexpected behavior label Nov 26, 2018
@acid-chicken

This comment has been minimized.

Sign in to view
@AyaMorisawa

This comment has been minimized.

Sign in to view
@tateisu
Copy link

tateisu commented Nov 26, 2018

free -bw でワイド表示するとどうなりますか

@SanMurakami
Copy link
Contributor

SanMurakami commented Nov 26, 2018 •
edited
Loading

free -bw でワイド表示するとどうなりますか

image

@acid-chicken acid-chicken self-assigned this Nov 26, 2018
@acid-chicken
Copy link
Member

@CookieRamen Can you provide stdout of free -V command?

@tateisu
Copy link

tateisu commented Nov 26, 2018

あとはlinuxだと分かってるなら /proc/meminfo を読むとか

@tateisu
Copy link

tateisu commented Nov 26, 2018

実装の違いを意識してあれこれしてるのはsysteminformationパッケージの時点で同じだからね

@tateisu
Copy link

tateisu commented Nov 26, 2018

RAM 128GBの時点で表示桁数から変わってしまうはず。freeのアップデートを待つの？

@SanMurakami
Copy link
Contributor

@CookieRamen Can you provide stdout of free -V command?

image

@tateisu
Copy link

tateisu commented Nov 26, 2018

RAM 16GBのマシンでBusyBox動かすなんて想定されてなかったんだろうな…

@SanMurakami
Copy link
Contributor

じゃあ8GBにしますか

@tateisu
Copy link

tateisu commented Nov 26, 2018

それで直るなら、後はsysteminformationパッケージにissue投げて終わり、でも別に良さそうな気はします

@tateisu
Copy link

tateisu commented Nov 26, 2018

別に systeminformation 側で /proc/meminfo 読んでもらってもいいので、原理的に不可能という話は全くありません

@tateisu tateisu mentioned this issue Nov 26, 2018
Closed
2 tasks
@tateisu
Copy link

tateisu commented Nov 26, 2018

https://bugs.busybox.net/show_bug.cgi?id=11521

@acid-chicken acid-chicken mentioned this issue Nov 26, 2018
Merged
AyaMorisawa pushed a commit that referenced this issue Nov 26, 2018
@acid-chicken @AyaMorisawa
Fix #3409 (#3410)
33243e7 
* Update Dockerfile

* Update Dockerfile
@AyaMorisawa
Copy link
Contributor Author

Misskey側では、Dockerfileの構成を変更することにより解決

@AyaMorisawa AyaMorisawa changed the title メモリの認識がおかしい メモリ容量の認識がおかしい Nov 28, 2018
@khws4v1 khws4v1 mentioned this issue Feb 9, 2019
Open
acid-chicken pushed a commit that referenced this issue Feb 10, 2019
@khws4v1 @acid-chicken
Docker: Remove unnecessary workaround for BusyBox's "free" (#4199)
7de1cf8 
systeminformation gets incorrect memory information due to BusyBox's
"free" issue.(#3409)
A workaround for avoiding it was made.

But it never works because the runner container has no effect.
It should be deleted.
acid-chicken added a commit that referenced this issue Feb 13, 2019
@acid-chicken
Docker: Remove unnecessary workaround for BusyBox's "free" (#4199) (#…
fa5ea45 
…4213)

systeminformation gets incorrect memory information due to BusyBox's
"free" issue.(#3409)
A workaround for avoiding it was made.

But it never works because the runner container has no effect.
It should be deleted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acid-chicken acid-chicken

Labels
🐛Bug Unexpected behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tateisu @AyaMorisawa @acid-chicken @SanMurakami