Skip to main content
Inspiring
October 28, 2014
Question

ColdFusion Builder 3 - Open a large file causing CF Builder 3 to Hang

  • October 28, 2014
  • 12 replies
  • 3915 views

When I try to open a large file having 2700 lines of code in CF Builder 3, it becomes completely unusable and in the task manager showing Not Responding.

This topic has been closed for replies.

12 replies

TechFuserAuthor
Inspiring
September 5, 2018

@charlie. I screwed up that chain - my apology.

@jascomp. [empty string]

TechFuserAuthor
Inspiring
September 5, 2018

Unlike many old RAMs, I am not OK to accept bugs are part of software, rather poor execution on the delivery of a product.

This I think is inline with Adobes interest in products like cfbuilder and clearly less than A ppl r in play.

TechFuserAuthor
Inspiring
September 5, 2018

here Is a snippet to jog ur over used RAM.

As a developer I understand that bugs are a part of software.  I get it.

Charlie Arehart
Community Expert
Community Expert
September 5, 2018

Techfuser: is your offered quote of "As a developer I understand that bugs are a part of software.  I get it" meant to be your reply to my asking you when I said anything about accepting buggy software (as you asserted I had said)? If so, note that you are quoting jascomp, not me.

/Charlie (troubleshooter, carehart. org)
TechFuserAuthor
Inspiring
September 3, 2018

@charlie. I moved on alright given Adobes future goal; that’s the wise thing to do!

I am only trying to make a point of ur pointless excuse that you would expect a product to be buggy and still pay for it. 

Charlie Arehart
Community Expert
Community Expert
September 5, 2018

Techfuser, I never said anything about anyone accepting let alone paying for buggy software. Dude, take your axe and grind it somewhere else, and stop putting words in my mouth. By both, you are showing yourself to be nothing but a troll here.

/Charlie

Sent via the Samsung Galaxy S7 active, an AT&T 4G LTE smartphone

null

/Charlie (troubleshooter, carehart. org)
TechFuserAuthor
Inspiring
September 3, 2018

@jascomp. Well I can tell u when this product came out of mother womb we didn’t know what to do with it but adopt the old dino dreamweaver.

maybe ur quip was quip-ical enough that now ur saying u don’t need any help with it.

Oracle is staying behind their product lines whether it’s oracle or Java. I only see Adobe is wanting to stay behind photoshop than ur so far working cfbuilder.

jascomp
Known Participant
September 3, 2018

@TechUser I'm happy "enough".  I'll carve the code into stone using a hammer and chisel if that is what the client wants.  Right now the problem seems resolved, but as previously stated I've had this problem (or at least a similar manifestation of it) in every version of CFBuilder since version 1.0.  So, no I'm not confident that the issue is resolved.   You're correct that a paid for software upgrade should not be the solution.  However, for expedience it's probably worth it for some to simply go that route and move on.  I'm sure Charlie Arehart​ support offer extends to ANYONE having this problem.  If you can reliably reproduce the issue for him; I'm positive he can find the solution.

TechFuserAuthor
Inspiring
September 3, 2018

@jasconp. if its wotking for u now 99% of the time then maybe u should have waited bfr reacting too quickly with ur initial post. Obviously now u seem to be happy enough.

For me when I started this product at its inception, it  was so buggy that we felt there was no point of looking at it agian.

And with Adobes recent direction with other products like Flash, it is clear for me to think Adobe will not have their A team on products like this compared to a Photoshop. My 2cents.

jascomp
Known Participant
September 3, 2018

@TechFuser Glad you found tools that work better for you.  Adobe like any company is going to focus on what generates revenue.  In this case that does appear to be other higher profile products.  Personally I've never found any Adobe product I've used over the years to be so buggy that it was unusable.  I think you read too much into my initial quip.  I wasn't completely disillusioned as you appear to be; just a bit frustrated to still be encountering an issue that has been around for quite some time.  To be fair I still encounter Microsoft and Oracle bugs that have been around for years (and it is just as frustrating).  Just the nature of software bro

TechFuserAuthor
Inspiring
September 3, 2018

@charlie. I do not think it’s ok to accept a buggy product when ppl r paying premium for it and continue to use it less productivity hoping in the next version bugs will be addressed.

I only know one person who would buy a denim with zipper that sorta works and continue to live with it hoping next year the denim will have a better zipper abd then buy it again.

I can see denim having some unexpected wrinkles but a poorlot made denim - why would u buy it let alone use it for years. There is no rational behind it!

If a a product is rolled out of development to ptoduction, then I could “get it”. Softwares r buggy. And maybe thats how it has been working for Adobe from what I hear from u. 

@jascomp. Not sure I understand if u burnt ur tounge and thought product was just fine 3 days in bcz ur all numb now or it was just an unrealized commotion from having to sip a hot cup of joe.

jascomp
Known Participant
September 3, 2018

@TechUser I think my rational (or perhaps better said:  my clients rational) is that the zipper works 99% of the time and works well.  There's just no ROI in ripping it off to replace it with one that might work 99.9% of the time.  LOL though you may be right in that I'm now numb to dealing with Adobe bugs .

jascomp
Known Participant
September 2, 2018

Update:  3 days into using CF Builder 2018.  So far no issues.

Charlie Arehart
Community Expert
Community Expert
September 3, 2018

Good to hear about the success with cfb 2018 so far, and thanks for the kind regards,  indeed on behalf of the many folks in the community who help, as you allude to.

null

/Charlie (troubleshooter, carehart. org)
TechFuserAuthor
Inspiring
September 2, 2018

@bkbk. for me not getting enough positive response or even a response that it would it be addressed in the future was enough to not continue to use cfbuilder.

I just felt it was built in a cheap way over eclipse with all th bugs not addressed bfr releasing - that our company actually paid for 3 developers license. It was just a waste of company money.

jascomp
Known Participant
September 2, 2018

I actually enjoy using CFBuilder (most of the time).  Despite the bugs I've found it to be a handy editor.  I've used many Adobe products over the years and have consistently found their support and bug resolution lacking at best.  More often I find my solutions within the online community.  As a developer I understand that bugs are a part of software.  I get it.  However, having those bugs move from version to version with plenty of reports to Adobe and no resolution is apparently just how Adobe operates.  The reason I've stuck with Adobe and specifically ColdFusion despite what a reasonable person would tolerate is that I maintain a lot of legacy code that is simply never going to be refactored and the community.  As you can see from previous responses; community members like Charlie Arehart step up and pick up the slack left by Adobe.

TechFuserAuthor
Inspiring
August 30, 2018

If I recall correctly, this issue was more apparent when you have an entire file system mapped to a drive and you are accssing large files from that mapped drive with cfbuilder.

I gave up on cfbuilder and still use dreamweaver.

Charlie, is it?!

BKBK
Community Expert
Community Expert
September 2, 2018

techuser​ and @jascomp, thank you for sharing your experience with ColdFusion Builder. One remark I should like to add is that you make no reference to bug-fixes. Therefore, you're assuming implicitly that Builder development has stood still across a period of years. That is, of course, not so.

ColdFusion Builder, like every other software used by developers, evolves frequently. The issues you mention have likely been solved in the current version. If so, then reports such as yours would no doubt have contributed to the solution.

So, I would say, report in the bug database any issues you find. Follow up their progress, and have faith that you are contributing to improve the software.