[Mono-bugs] [Bug 75839][Nor] New - Prior version of ~/.wapi can cause lockup with new runtime

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Aug 18 00:56:12 EDT 2005

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by mathpup at mylinuxisp.com.


--- shadow/75839	2005-08-18 00:56:12.000000000 -0400
+++ shadow/75839.tmp.17193	2005-08-18 00:56:12.000000000 -0400
@@ -0,0 +1,63 @@
+Bug#: 75839
+Product: Mono: Runtime
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: mathpup at mylinuxisp.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Prior version of ~/.wapi can cause lockup with new runtime
+Description of Problem:   
+Recent versions of Mono leave behind files in ~/.wapi. If a user runs a 
+32-bit x86 version of Mono, the resulting ~/.wapi files cause problems 
+when a 64-bit x86 (x86_64) version of Mono is later executed. 
+Specifically, the Mono runtime freezes, using almost all CPU time. 
+Deleting the old ~/.wapi directory seems to fix the problem. 
+Although the remedy (deleting the .wapi directory) is simple, it might not 
+be immediately obvious. I do not know exactly when Mono began persisting 
+these files, so some users might not have experienced this yet. Some kind 
+of sanity check would really be nice to avoid this. In my case, I have 
+been tracking the SVN version of Mono on my i686, and then I recently 
+upgraded to an x86_64, running SUSE 9.3 in 64-bit mode. I retained the 
+data in /home, including the .wapi directory.  
+Steps to reproduce the problem:   
+1. Install 32-bit version of version of Mono. (I used the binary of 
+mono- from http://www.go-mono.com.) 
+2. Run mcs --version (or any command that causes the runtime to create 
+files in ~/.wapi.) 
+3. Remove 32-bit version of Mono. 
+4. Install 64-bit version of Mono. (I installed mono- from source). 
+5. Run mcs --version. 
+Actual Results:   
+Terminal freezes. Mono consumes almost all CPU time. 
+Expected Results:   
+Prints ``Mono C# compiler version'' 
+How often does this happen?    
+Additional Information:   
+Let me know if you need a tarball of the ~/.wapi directory.

More information about the mono-bugs mailing list