hi, bram
when can this bug be fixed? I am waiting the crash fix for several
days.
thanks,
mike
On 3月14日, 下午2时31分, Christian Brabandt cbli...@256bit.org wrote:
On Tue, March 13, 2012 22:16, Bram Moolenaar wrote:
Christian Brabandt write:
On Sa, 10 Mär 2012, 驼峰 wrote:
my repro step:
Hi 驼峰!
Please don't top poste. This has been told you already several times.
See http://en.wikipedia.org/wiki/Posting_style for an explanation, what
this means.
On Fr, 16 Mär 2012, 驼峰 wrote:
when can this bug be fixed? I am waiting the crash fix for several
days.
This has just been fixed
On Tue, March 13, 2012 22:16, Bram Moolenaar wrote:
Christian Brabandt write:
On Sa, 10 Mär 2012, 驼峰 wrote:
my repro step:
1. run gvim
2. open NERDTree windows
3. create several tabs using 't' shortcut of NERDTree plugin
4. '1gt'
5, maximize gvim
6, '2gt'
7, restore the
Christian Brabandt write:
On Sa, 10 Mär 2012, 驼峰 wrote:
my repro step:
1. run gvim
2. open NERDTree windows
3. create several tabs using 't' shortcut of NERDTree plugin
4. '1gt'
5, maximize gvim
6, '2gt'
7, restore the windows size from maximize window to normal window.
8,
Thanks for the patch. I have been unable to reproduce the crash, I hope
someone can verify this patch fixes the problem.
Have you added autocmd
VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw? It is an
essential part.
I do wonder how row can be too big, perhaps there is a problem
Hi 驼峰!
On Sa, 10 Mär 2012, 驼峰 wrote:
my repro step:
1. run gvim
2. open NERDTree windows
3. create several tabs using 't' shortcut of NERDTree plugin
4. '1gt'
5, maximize gvim
6, '2gt'
7, restore the windows size from maximize window to normal window.
8, '1gt'
Result: after 8th step,
my repro step:
1. run gvim
2. open NERDTree windows
3. create several tabs using 't' shortcut of NERDTree plugin
4. '1gt'
5, maximize gvim
6, '2gt'
7, restore the windows size from maximize window to normal window.
8, '1gt'
Result: after 8th step, my gvim will crash definitely.
My take
驼峰 wrote:
I can 100% repro this bug by adding the following line into my vimrc.
autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw
The repro step:
1. open NERDTree
2. create multiple tabs.
3. switch tabs which contains NERDTree windows to other window.
4. If not crash,
I guess this only happens on Windows.
On Mar 10, 9:24 pm, Dominique Pellé dominique.pe...@gmail.com wrote:
驼峰 wrote:
I can 100% repro this bug by adding the following line into my vimrc.
autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw
The repro step:
1. open NERDTree
On Sat, 10 Mar 2012, 驼峰 wrote:
On Mar 10, 9:24 pm, Dominique Pellé dominique.pe...@gmail.com
wrote:
I can't reproduce it with vim-7.3.470 on Linux. No crash.
I also ran with Valgrind memory check and did not find problems.
Can you reproduce it by starting vim with vim -u NONE
and
my environment is:
1: gvim 32 bits
2: only with NERDTree plugin
3: only with the following contents in my vimrc
autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw
4: windows xp 32 bit.
my repro step:
1. run gvim
2. open NERDTree windows
3. create several tabs using 't' shortcut
My NERDTree version is 4.1.0.
On Mar 11, 10:45 am, 驼峰 guotuof...@gmail.com wrote:
my environment is:
1: gvim 32 bits
2: only with NERDTree plugin
3: only with the following contents in my vimrc
autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw
4: windows xp 32 bit.
my
On Sat, 10 Mar 2012, 驼峰 wrote:
my repro step:
1. run gvim
2. open NERDTree windows
3. create several tabs using 't' shortcut of NERDTree plugin
4. '1gt'
5, maximize gvim
6, '2gt'
7, restore the windows size from maximize window to normal window.
8, '1gt'
Result: after 8th step, my gvim will
I can't reproduce this on my 32bit Windows XP with my self-compiled vim
version 7.3.444.
On Thu, Mar 08, 2012 at 05:44:01PM -0800, 驼峰 wrote:
BTW, I tried using the gvim 7.3 without any patches(ftp://ftp.vim.org/
pub/vim/pc/gvim73.zip), the problem still happens.
I guess that nobody hit this
I can 100% repro this bug by adding the following line into my vimrc.
autocmd VimEnter,BufNew,BufEnter,BufWritePost,VimResized * redraw
The repro step:
1. open NERDTree
2. create multiple tabs.
3. switch tabs which contains NERDTree windows to other window.
4. If not crash, switch several times.
Guotuofeng wrote:
The full crash analyze is:
Opened log file 'd:\gvimcrash.txt'
0:000 k
ChildEBP RetAddr
003bf2e8 776af5c9 ntdll!RtlReportCriticalFailure+0x29
003bf2f8 776af6a9 ntdll!RtlpReportHeapFailure+0x21
003bf32c 7766a5cb ntdll!RtlpLogHeapFailure+0xa1
003bf374 776135a7
Hi, Bram,
Thanks for your reply. Actually, I am working in Windows and don't
have valgrind.
The crash can be easily reproed by using two plugins: NERDTree and
buf_it.
Their links are:
http://www.vim.org/scripts/script.php?script_id=1658
http://www.vim.org/scripts/script.php?script_id=2833
The
Hi,
I run into the following gvim crash happened when I try to switch to other tabs
by using 1gt or 2gt if NERDTree is opened.
the crash is:
ChildEBP RetAddr
003bf2e8 776af5c9 ntdll!RtlReportCriticalFailure+0x29
003bf2f8 776af6a9 ntdll!RtlpReportHeapFailure+0x21
003bf32c 7766a5cb
The full crash analyze is:
Opened log file 'd:\gvimcrash.txt'
0:000 k
ChildEBP RetAddr
003bf2e8 776af5c9 ntdll!RtlReportCriticalFailure+0x29
003bf2f8 776af6a9 ntdll!RtlpReportHeapFailure+0x21
003bf32c 7766a5cb ntdll!RtlpLogHeapFailure+0xa1
003bf374 776135a7 ntdll!RtlpCoalesceFreeBlocks+0x84c
19 matches
Mail list logo