Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Mon May 05, 2008 10:56 pm   

Did everyone get a chance to test this over the weekend?
 
On one level I'm happy because after the 3-day weekend, I haven't seen very many big problem reports for 2.24.

On another level I'm worried because maybe people didn't have time to do much testing this past weekend.

I'm going to release the 2.24 Public version on Wednesday. That's definite. It will always still have some bugs no longer how much more I try to fix. And I firmly believe that 2.23 is far more stable that the current 2.18 Public version.

So you only have one more day to report any problems that you think must be fixed for the public version.
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Mon May 05, 2008 11:26 pm   
 
Zugg,
All of the quirky little problems that were to do with those packages I sent you are no longer there. I did an export/import to xml before I installed them to 2.23 and so far they've worked without a hassle. (I'd done that once before but it hadn't fixed it. I hadn't done it for 2.22 though, which I suppose was a failure on my end).

I thought it might be easier just to tell you here, rather than bringing the original threads on it back to the top of the list and perhaps causing people to read through them entirely.

So far I've only had one crash with v2.23, and I am fairly sure it was linked to one of the bugs Vijilante posted about, but I couldn't reproduce it and it hasn't happened since, so nm.

.. so well done Razz
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
Arminas
Wizard


Joined: 11 Jul 2002
Posts: 1265
Location: USA

PostPosted: Mon May 05, 2008 11:57 pm   
 
I've only had one or two new problems, and since I've been playing I've not reported em.

They are not caused by the new stuff, I wrote new code and I think the code isn't sound.

Anyway expect a bug report in a week or two regarding mxp send showing up on the next line when using sub.
That and maybe a post or two from me regarding color bleeding to the next line. -> This is a very old problem so no rush on either thing.
Thing is that they both appear to be related.

These things were not caused by any changes in the last couple of versions at any rate!

I've been playing a lot, played most of the weekend in fact.
Part of creating that new code I spoke of I keep losing data saved to a particular database variable.
Only that one used in the part of code that is bleeding in the regex. This is new, but it is also part of new code.

I was going to wait until after the public release to post. Still plan to unless you tell me to report em now.
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram
Reply with quote
Vijilante
SubAdmin


Joined: 18 Nov 2001
Posts: 5182

PostPosted: Tue May 06, 2008 1:30 am   
 
Sorry I didn't get to really working at proper testing much. I was rather focused on trying to sort out the dll issues, and make final updates with the subregex code. Now I am focusing on perfecting the damn quote handling for %1 in the compatibility report, I am not quite happy with it yet.
_________________
The only good questions are the ones we have never answered before.
Search the Forums
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Tue May 06, 2008 1:54 pm   
 
I used it extensively over the weekend. Except for the ATCP bleeding and reverting variables it has been just fine.
Reply with quote
JQuilici
Adept


Joined: 21 Sep 2005
Posts: 250
Location: Austin, TX

PostPosted: Tue May 06, 2008 7:39 pm   
 
I have been playing around 6-8 hours with 2.23, and I am happy to report that I have not found any serious NEW problems. The only real goofiness that I found turned out to be related to a duplicated variable (not sure when it got duplicated, and it hasn't recurred).

So it looks good to me. I'll try to verify any of my previously-reported bugs that are fixed in 2.23.
_________________
Come visit Mozart Mud...and tell an imm that Aerith sent you!
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Tue May 06, 2008 9:31 pm   
 
JQuilici wrote:
The only real goofiness that I found turned out to be related to a duplicated variable (not sure when it got duplicated, and it hasn't recurred).

:( Its almost always a duplicate variable/alias that goes ummissed for a while, then rears its head to confusingly make my curing fail miserably at the worst possible moment.

I don't blame Zugg though; its my fault for relying too much on scoping. I'm slowly changing my scripting habits to use less cross-package stuff, with more events. Eventually I'd like most packages to be almost completely independent of each other. Sometimes its hard to figure out where stuff belongs though.
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
tijer
Novice


Joined: 17 Jun 2006
Posts: 45

PostPosted: Wed May 07, 2008 11:11 am   
 
Still getting crashes with closing of sessions that has been happening since 2.20

See the following

Code:

Date/time         : 2008-05-07, 12:03:50, 211ms
computer name     :
user name         :
registered owner  :
operating system  : Windows Vista Service Pack 1 build 6001
system language   : English
system up time    : 12 hours 55 minutes
program up time   : 12 hours 45 minutes
processors        : 2x Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
physical memory   : 812/2045 MB (free/total)
free disk space   : (C:) 193.82 GB
display mode      : 1440x900, 32 bit
process id        : $be4
allocated memory  : 68.55 MB
executable        : cMUDPro.exe
exec. date/time   : 2008-05-01 23:13
version           : 2.23.0.0
compiled with     : BCB 2006/07
madExcept version : 3.0h
contact name      :
contact email     :
callstack crc     : $e3f72b45, $15da6ee1, $15da6ee1
exception number  : 1
exception class   : Exception
exception message : Error saving data in background - COMMIT TRANSACTION SQL Error: cannot commit - no transaction is active.

Main ($1a44):
00ea7139 +20d cMUDPro.exe  PkgDM           4608  +39 TPkg.Save
00d7874b +01f cMUDPro.exe  PARENT          9053   +3 CloseModule
00d78951 +1e1 cMUDPro.exe  PARENT          9093  +36 TParentForm.CloseSession
00d7ea5d +011 cMUDPro.exe  PARENT         11532   +2 TParentForm.WMCloseSession
004bb0d7 +2bb cMUDPro.exe  Controls        5146  +83 TControl.WndProc
004bf0db +4fb cMUDPro.exe  Controls        7304 +111 TWinControl.WndProc
004a163b +553 cMUDPro.exe  Forms           3512 +136 TCustomForm.WndProc
00d161e8 +020 cMUDPro.exe  DXSounds        2128   +9 TCustomDXSound.FormWndProc
00d1398c +00c cMUDPro.exe  DXClass          635   +1 TControlSubClass.WndProc
004be804 +02c cMUDPro.exe  Controls        7073   +3 TWinControl.MainWndProc
0047c448 +014 cMUDPro.exe  Classes        11583   +8 StdWndProc
76c4b9fc +016 USER32.dll                             CallWindowProcA
006d34a3 +0a7 cMUDPro.exe  aqDockingUtils  1728   +7 CallDefWndProc
006d3591 +0dd cMUDPro.exe  aqDockingUtils  1776  +41 TaqWindowEventFilter.WndProc
0047c448 +014 cMUDPro.exe  Classes        11583   +8 StdWndProc
00405152 +002 cMUDPro.exe  System          9513   +0 @ClassDestroy
76c4b9fc +016 USER32.dll                             CallWindowProcA
006d34a3 +0a7 cMUDPro.exe  aqDockingUtils  1728   +7 CallDefWndProc
006d3591 +0dd cMUDPro.exe  aqDockingUtils  1776  +41 TaqWindowEventFilter.WndProc
0047c448 +014 cMUDPro.exe  Classes        11583   +8 StdWndProc
76c35a27 +00a USER32.dll                             DispatchMessageA
004a97b0 +0fc cMUDPro.exe  Forms           8105  +23 TApplication.ProcessMessage
004a97ea +00a cMUDPro.exe  Forms           8124   +1 TApplication.HandleMessage
004a9adf +0b3 cMUDPro.exe  Forms           8223  +20 TApplication.Run
00ef9194 +088 cMUDPro.exe  cMUDPro          352  +20 initialization
76b8490f +010 kernel32.dll                           BaseThreadInitThunk

error details:
closing of a session


Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Wed May 07, 2008 4:31 pm   
 
tijer: please create a separate forum post for bug reports. Include the exact procedure you used to get the crash.

Btw: That particular crash is caused by having two sessions that share the same *.pkg file open at the same time and then closing the session. Make sure you don't have multiple windows sharing the same pkg file...that can lead to all sorts of problems, like the settings of one window being lost when the other window saves to the same package file.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net