Bad Java?? Making grown men cry

Kellyk126

I don't know if I have bad codes, or codes that are making each other bog down my page, but when my page is open, even if I just have it open on the homepage, it bogs down my entire system and ends up freezing, is there any way to fix it, to run more smoothly? Is it because I have a slideshow? If someone could take a look at my page that would be wonderful, thank you in advance.

www.kellykoziolphotography.com

Steve Cavigliano

Hi Kelly,
The good news is this seem to be a problem for you only. I went to your site and it totally loaded (slideshow started playing) in less than 3 seconds. It also went from page to page quickly too. This was from my home DSL which isn't all that fast.

Please try ridding Firefox of it's old temporary files, by clearing them. This should help your pager loading. If it doesn't there may be some connection issues at play. So contact the Help Desk and we will have you run a few tests to see if we can pinpoint the problem.

Cavig

Allen

Kellyk126 wrote:

I don't know if I have bad codes, or codes that are making each other bog down my page, but when my page is open, even if I just have it open on the homepage, it bogs down my entire system and ends up freezing, is there any way to fix it, to run more smoothly? Is it because I have a slideshow? If someone could take a look at my page that would be wonderful, thank you in advance.

www.kellykoziolphotography.com

Remove this from your flash slideshow script code. To not have a splash the line has to
be removed or it sucks 100% of CPU.

splash: 'none',

jfriend

Allen wrote:

Remove this from your flash slideshow script code. To not have a splash the line has to
be removed or it sucks 100% of CPU.

splash: 'none',

I'm really disappointed that Smugmug has not fixed this yet. We first brought it to their attention a long time ago. I don't even remember if they think it's worth doing anything about.

Good defensive coding techniques should guard against doing bad things to your system if given bad input parameters from the user.

ashishpandey

jfriend wrote:

I'm really disappointed that Smugmug has not fixed this yet. We first brought it to their attention a long time ago. I don't even remember if they think it's worth doing anything about.

Good defensive coding techniques should guard against doing bad things to your system if given bad input parameters from the user.

The real disappointing part is not that such a thing is not fixed. The real disappointing part is that you would never have got anything beyond a "we'll see" response (or none at all). That's the trend I see often on the so called bug reporting thread

It is not even something that is on their support task list. You / Allen can spot it so quickly (and I have observed it in some earlier threads too) because you are concerned and know where to look; while someone from smugmug is still not looking in that corner

Andy

jfriend wrote:

I'm really disappointed that Smugmug has not fixed this yet. We first brought it to their attention a long time ago. I don't even remember if they think it's worth doing anything about.

Good defensive coding techniques should guard against doing bad things to your system if given bad input parameters from the user.

Hello John, ouch I'm so sorry you are disappointed in us. As I mentioned to you in prior emails and posts, on your good suggsetion I spent time with Shizam on this and that it's in process. There are perfectly good reasons why certain things come out to live site before others.

I'm sorry this upsets you so much, and I'm sorry you are disappointed

Andy

ashishpandey wrote:

The real disappointing part is not that such a thing is not fixed. The real disappointing part is that you would never have got anything beyond a "we'll see" response (or none at all).

Hello Ashish, what you aren't aware of is the many conversations between us and John

You have things in the bug thread, they've been acknowledged and Dustin our bug-man is on top of them. Beyond that, i'm not sure what you want us to do, expectations-wise. We're a small, bootstrapped company, and for 6 years running now, we've grown by listening to our customers and by being responsive to bugs as well. We won't let you down either.

Allen

I got Ivar to add a warning to the wiki page.

splash: '<url>'[LIST]
[*][COLOR=#009900]Url to an image you want to set as your splash image[/COLOR]
[*][COLOR=#3333ff]Default: blank[/COLOR]
[*][COLOR=#990000]URL must use #46; instead of any dots '.'[/COLOR]
[*][COLOR=red]Remove this line if you don't want a splash 
[/COLOR][/LIST]

 

Looks like it would be a good idea to add the warning to the tutor page also in big red font.

Kellyk126

Thank you all for suggestions and help, you are all so wonderful!! I'm going to try clearing out that line in my bio, and clearing everything out of firefox as well. I also emailed the helpdesk and they promptly responded, I ran tests on both my work computer and my home computer, and apparently they are both slow? Which is weird since I have a brand new studio laptop at home (darn should have gone with the faster, bigger, better I guess)

Anyways, crossing my fingers, thanks again!

jfriend

Allen wrote:

I got Ivar to add a warning to the wiki page.

splash: '<url>'[LIST]
[*][COLOR=#009900]Url to an image you want to set as your splash image[/COLOR]
[*][COLOR=#3333ff]Default: blank[/COLOR]
[*][COLOR=#990000]URL must use #46; instead of any dots '.'[/COLOR]
[*][COLOR=red]Remove this line if you don't want a splash 
[/COLOR][/LIST]
 

Looks like it would be a good idea to add the warning to the tutor page also in big red font.

Good idea. Hopefully that will help some for future slideshow users.

jfriend

Andy wrote:

Hello John, ouch I'm so sorry you are disappointed in us. As I mentioned to you in prior emails and posts, on your good suggsetion I spent time with Shizam on this and that it's in process. There are perfectly good reasons why certain things come out to live site before others.

I'm sorry this upsets you so much, and I'm sorry you are disappointed

Usually some things come out before others because that's the way you set your priorities. I'm expressing a disagreement with how bugs are prioritized vs. those other things. From the outside, it appears that the new lab took way longer than anticipated and sucked up a lot of resources and there wasn't much attention paid to bug fixing elsewhere in the site during that time.

Besides protecting your own users and their viewers from this issue, there is significant potential PR damage from this bug. All that has to happen is that someone influential writes "I went to a Smugmug-hosted photo site and it took over my PC, taking 100% of my CPU so I could barely do anything else on my computer. For now, I would avoid Smugmug or photo sites hosted by them as this is a pretty serious problem with their site." I'm just surprised nobody at Smugmug seems to mind leaving this timebomb sitting out there in a bunch of user's accounts for this long. I don't know if you don't understand the damage potential or just don't think it's that important or just kind of forgot about it for awhile while trying to get all the other things done. Months ago, I would have put this in the category of bugs that we should fix in our next push (no longer than a week or two). You chose differently.

ashishpandey

Andy wrote:

We won't let you down either.

Sound's like you are out there to prove me wrong, and for once I am very happy about that

as you say, I may not be aware about some conversations - so apologies if I am drawing wrong conclusions in a very short period here. with time I will get it

Andy

jfriend wrote:

Usually some things come out before others because that's the way you set your priorities. I'm expressing a disagreement with how bugs are prioritized vs. those other things. From the outside, it appears that the new lab took way longer than anticipated and sucked up a lot of resources and there wasn't much attention paid to bug fixing elsewhere in the site during that time.

Besides protecting your own users and their viewers from this issue, there is significant potential PR damage from this bug. All that has to happen is that someone influential writes "I went to a Smugmug-hosted photo site and it took over my PC, taking 100% of my CPU so I could barely do anything else on my computer. For now, I would avoid Smugmug or photo sites hosted by them as this is a pretty serious problem with their site." I'm just surprised nobody at Smugmug seems to mind leaving this timebomb sitting out there in a bunch of user's accounts for this long. I don't know if you don't understand the damage potential or just don't think it's that important or just kind of forgot about it for awhile while trying to get all the other things done. Months ago, I would have put this in the category of bugs that we should fix in our next push (no longer than a week or two). You chose differently.

Hey John,

Our wiki says 'Remove this line if you don't want a splash' where do people get Splash: 'none', from?

jfriend

Andy wrote:

Hey John,

Our wiki says 'Remove this line if you don't want a splash' where do people get Splash: 'none', from?

I believe that additional line inn the wiki was only added to the wiki yesterday (see Allen's posting earlier in this thread).

Besides, the problem occurs in other ways too besides putting "none" there. I helped someone fix their site yesterday that had put their name in that field. Nobody told them they could or couldn't do that, they just decided that's what they wanted to do.

The point is that any code that takes inputs from users should expect it is occasionally going to get bad input and shouldn't take your system down when that happens. And, because there are lots of users putting in slideshows that know absolutely nothing about javscript, bad inputs happen even more frequently here than other places.

I think there are also lots of users adding slideshows from a tutorial and they've never seen the wiki. Info about customization is in a lot of places so it's pretty easy to see one piece of information and not know that the others even exist. And, anyone here on dgrin knows that there are lots of users who either don't read the instructions or don't follow them very well. Software should certainly not assume that users are going to follow directions perfectly.

Andy

jfriend wrote:

Usually some things come out before others because that's the way you set your priorities. I'm expressing a disagreement with how bugs are prioritized vs. those other things. From the outside, it appears that the new lab took way longer than anticipated and sucked up a lot of resources and there wasn't much attention paid to bug fixing elsewhere in the site during that time.

Besides protecting your own users and their viewers from this issue, there is significant potential PR damage from this bug. All that has to happen is that someone influential writes "I went to a Smugmug-hosted photo site and it took over my PC, taking 100% of my CPU so I could barely do anything else on my computer. For now, I would avoid Smugmug or photo sites hosted by them as this is a pretty serious problem with their site." I'm just surprised nobody at Smugmug seems to mind leaving this timebomb sitting out there in a bunch of user's accounts for this long. I don't know if you don't understand the damage potential or just don't think it's that important or just kind of forgot about it for awhile while trying to get all the other things done. Months ago, I would have put this in the category of bugs that we should fix in our next push (no longer than a week or two). You chose differently.

Being fixed, just checked with Shizam and it's part of a release (soon) that'll have a bunch of slideshow stuff and flash stuff in it.

Your patience is appreciated. We may not always hop to you it on your command, but we listen to every single word, John and we get to everything in time.

Pretty darn good for a bootstrapped company.

We really appreciate your vigilance :jfriend

Allen

jfriend wrote:

I believe that additional line inn the wiki was only added to the wiki yesterday (see Allen's posting earlier in this thread). ...

It was added Oct 28, 2008 according to the wiki change history.

jfriend

Allen wrote:

It was added Oct 28, 2008 according to the wiki change history.

Then, I guess it proves how few people know about or read the documentation :cry.

Andy

jfriend wrote:

Then, I guess it proves how few people know about

P1 of the slideshow leads them to it. The tutorial leads them to it.

Man, this 'll all be easier when we have a box on the homepage for a slideshow, won't it?

jfriend

Andy wrote:

P1 of the slideshow leads them to it. The tutorial leads them to it.

Well, we've once more proven what percentage of the population sits down and reads directions before trying something. I love Tim Allen's quote (from the TV show Home Improvement) on this subject:

"Directions? Hmmmph! Those are just one man's opinion on how you do it."

This is usually said to his wife as smoke is pouring out of the thing he's trying to fix/assemble and she's giving him a look.

Andy wrote:

Man, this 'll all be easier when we have a box on the homepage for a slideshow, won't it?

Yep - no doubt.

I hope an automatic way to do the separate galleries page comes at the same time because that's another one that some people don't seem to be able to follow the directions on. It's darn simple if you just follow the directions, but you do have to know your way around the different pieces of customization and...

Andy

jfriend wrote:

Well, we've once more proven what percentage of the population sits down and reads directions before trying something. I love Tim Allen's quote (from the TV show Home Improvement) on this subject:

"Directions? Hmmmph! Those are just one man's opinion on how you do it."

We have a saying here: "Reading is Hard"