RE: FusionDebug Group: FusionDebug crashes after a while on Mac OS X 10.5.6 (Intel)

[charlie arehart]

Great to hear that you've heard good things, as a fellow user. :-)

As for your problem, I'm not on a Mac, so maybe someone else can speak up,
but I'm curious: are you in the midst of a debugging session when you try to
save the file? More to the point, is the debugger stopped at a breakpoint
with a running program? Not that it should matter, but it just seems a
useful point.

You say the error is when saving a file, and really, saving a file should be
an Eclipse task (this "complete IDE" is just Eclipse with FusionDebug and
CFEclipse both bundled atop it. Eclipse is the editor, responsible for
saving files.) Even the setting of breakpoints (and therefore saving them
with a file) is an entirely Eclipse operation, since it does the same thing
for Java debugging.

Maybe someone from Intergral will pipe up with some aspect of FD that does
in fact step in the middle of a save operation. Until then, if you can add
any clarification, it may help.

Of course, the fact that you're running Railo is also pretty unique, as
that's a newly supported server. You may want to clarify specifically what
version of FD (and Eclipse, and Railo) you're using, in case that also may
be significant (unless an FD engineer speaks up first and recognizes
something with just what you've shared).

/charlie


-----Original Message-----
From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
Behalf Of FusionDebug newbie
Sent: Wednesday, March 11, 2009 10:30 AM
To: FusionDebug
Subject: FusionDebug Group: FusionDebug crashes after a while on Mac OS X
10.5.6 (Intel)


Hi,

I recently installed the FusionDebug complete IDE since I heard good
things about it. I've been using it for a couple of days and
everything seemed to work fine. However, right now when I go to save
a file the program just hangs. I don't know what's wrong since it was
working a few days ago. I'm using a MacBook Pro running Mac OS X
Leopard, with Railo as my CF application server. Below are the
messages I get when I Force Quit the application.

"The application J2SE 5.0 quit while unresponsive"

FusionDebug specific error message:

JVM terminated

Exit code=143
....

-Xms40m
-Xmx256m
....

Let me know if you need any more info. I didn't type in the whole
FusionDebug error message.

Thanks!

[FusionDebug newbie]

Thanks for your response Charlie!

I wasn't in a debugging session, just writing coldfusion code. You're
right that this might be a Eclipse/CFEclipse problem. The file that
I'm working on was getting to be long with multiple database queries,
cfscripts, and cfif statements. On save, the editor does appear to do
some simple parsing to make sure syntax is correct. This might be a
memory management issue and a solution would be to increase the memory
available to FusionDebug. However, I'm not sure how to do that. I've
looked at the config.ini file in the configuration directory of
FusionDebug, but it didn't have entries similar to an eclipse.ini
file. I have 4GB of memory.

I don't think the application server comes into play when I'm saving a
file. For example, I've worked on other files and saved them without
starting up Railo/Resin. It's only for testing a page when the app
server should be relevant. In any case, I'm running Resin 3.1.2 and
Railo 3.0.2. I downloaded the latest version of FusionDebug available
on the website, which is 2.0.1 and whatever Eclipse and CFEclipse
versions that come with it.

Thanks again!

On Mar 11, 12:24 pm, "charlie arehart" <charlie_li...@carehart.org>
wrote:

[charlie arehart]

Thanks for the clarifications, anonymous. Let's see if the FD folks (or
others) have any thoughts.

/charlie

-----Original Message-----
From: fusio...@googlegroups.com [mailto:fusio...@googlegroups.com] On
Behalf Of FusionDebug newbie
Sent: Thursday, March 12, 2009 2:16 AM
To: FusionDebug
Subject: FusionDebug Group: Re: FusionDebug crashes after a while on Mac OS
X 10.5.6 (Intel)

[Darren Pywell [FusionDebug Team]]

Hi Guys,

Doesn't sound like a problem in the debugger. I'm fairly confident on
that because in the next version (which hasn't been released yet) we
are adding "debugging support" for other engines. The first
implementation will be for Railo. You should be able to perform save
actions during debugging but one thing to remember is that the
debugger doesn't hot code the changes that you make into the running
page so you have to rerun the page to debug changes that you have
made...

JVM exit 143's are "Unexpected JVM exit" codes and these are usually
caused by one of three reasons, either:

1. The process was killed (by another process or a kill command for
example)
2. The JVM ran out of memory at a critical point and crashed
3. The JVM has a bug

I would recommend increasing the memory and moving up to a later JVM
to see if that doesn't help.

Cheers,
Darren



On Mar 12, 6:17 pm, "charlie arehart" <charlie_li...@carehart.org>
wrote: