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.

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

Crashes when using command-t in vim #89

Closed
sergevm opened this issue Oct 24, 2011 · 1 comment
Closed

Crashes when using command-t in vim #89

sergevm opened this issue Oct 24, 2011 · 1 comment

Comments

@sergevm
Copy link

sergevm commented Oct 24, 2011

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.

@luislavena
Copy link
Member

Hello,

Please post the issue and details about reproducing it to RubyInstaller group:

http://groups.google.com/group/rubyinstaller/

The problem you're describing is external to Ruby and is triggered by certain combination of elements.

As described on Issue #39, RubyInstaller only packages Ruby, but we might be able to help determine the root issue.

I'm closing this out as is not a bug of RubyInstaller itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants