summaryrefslogtreecommitdiff
path: root/po/ja.po
diff options
context:
space:
mode:
authorSebastien Helleu <flashcode@flashtux.org>2013-12-01 08:37:22 +0100
committerSebastien Helleu <flashcode@flashtux.org>2013-12-01 08:37:22 +0100
commit9a160509d74c521f2de005e0daf3762866ef8e04 (patch)
treefbb18ae34201162eec9e3352e6d903d6aaf7cd8f /po/ja.po
parent983791de847a93e487aa28b8397bb12ee4b0f17b (diff)
downloadweechat-9a160509d74c521f2de005e0daf3762866ef8e04.zip
core: fix random crash when closing a buffer
The problem happened because we used a pointer to a "struct t_gui_buffer_visited" for the switch to another buffer, when the buffer is closed. This is executed in all windows displaying the buffer, but on each switch to buffer, the visited buffers are updated and therefore the address can change. The pointer becomes invalid, and WeeChat still uses it on next windows for the buffer switch. It happened rarely because the visited buffer is freed and allocated immediately after, so the address is often the same in memory. Thanks to silverd for the tests on OS X to track the problem.
Diffstat (limited to 'po/ja.po')
0 files changed, 0 insertions, 0 deletions