You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I experience severe problems using command-t in vim on Windows 7 (the plugin is implemented in ruby), because of crashing of msvcrt-ruby191.dll (version is 1.9.2.290).
The error description I get is "The application has requested the Runtime to terminate in an unusual way".
I did make sure that the plugin (command-t) as well as vim use the very same version, by recompiling vim on my machine.
I have seen in another closed ticket (#75) that this may be related to some threading issues in the msvcrt-ruby191 dll ... The ticket was closed (because of the lack of response by the original issuer I believe). Any timing on a fix of this issue?
Thanks.
The text was updated successfully, but these errors were encountered:
I experience severe problems using command-t in vim on Windows 7 (the plugin is implemented in ruby), because of crashing of msvcrt-ruby191.dll (version is 1.9.2.290).
The error description I get is "The application has requested the Runtime to terminate in an unusual way".
In the event viewer, I get this information:
Faulting application name: gvim.exe, version: 7.3.277.0, time stamp: 0x4ea5ce84
Faulting module name: msvcrt-ruby191.dll, version: 1.9.2.290, time stamp: 0x4e20c10f
Exception code: 0x40000015
Fault offset: 0x00038039
Faulting process id: 0xc28
Faulting application start time: 0x01cc928e02b526ec
Faulting application path: C:\Program Files\Vim\vim73\gvim.exe
Faulting module path: C:\Tools\Ruby\Ruby192\bin\msvcrt-ruby191.dll
Report Id: 4b76da4c-fe81-11e0-a77b-00250053637e
I did make sure that the plugin (command-t) as well as vim use the very same version, by recompiling vim on my machine.
I have seen in another closed ticket (#75) that this may be related to some threading issues in the msvcrt-ruby191 dll ... The ticket was closed (because of the lack of response by the original issuer I believe). Any timing on a fix of this issue?
Thanks.
The text was updated successfully, but these errors were encountered: