Loading Profile...
Serious feedly bug - crashes 3.1 beta with tracemonkey on 1.2.55
Me again, running ff 3.1 beta with tracemonkey.
Your patch 1.2.55 created a serious error. I can't open FF 3.1 it bombs when you try to open it and it tries to download 1.2.55. This occurs each time you attempt to open it -- its not just the first time.
I assume it was trying to load and install 1.2.55. Anyway, I was able to open FF 3.0.3. It d/l and opened the feedly update. Then when I reopened FF 3.1 feedly 1.2.55 was already installed and everything was OK. (Haven't tried feedly yet to see if it actually works.)
Michael
Your patch 1.2.55 created a serious error. I can't open FF 3.1 it bombs when you try to open it and it tries to download 1.2.55. This occurs each time you attempt to open it -- its not just the first time.
I assume it was trying to load and install 1.2.55. Anyway, I was able to open FF 3.0.3. It d/l and opened the feedly update. Then when I reopened FF 3.1 feedly 1.2.55 was already installed and everything was OK. (Haven't tried feedly yet to see if it actually works.)
Michael
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Is tracemonkey on by default on 3.1 beta or do you have to do something special to turn it on?
-
Inappropriate?One more question Michael: how many people do you follow in feedly? I am trying to guess what is the size of the recommendation stream that feedly downloads when it starts to see if the crash you are seeing is similar to the previous crash report.
-
Inappropriate?Update: pushed out 1.2.56 where for firefox 3.1 we reduced the max size of the recommendation scream from 5MB to 1.5MB. If you have the time, can you please restart firefox 3.1 and see if you see the crash? And if so can you please report the crash to firefox, restart the browser and in about:crashes find the report ID and past is here? The report will allow us to determine if it is the same crash as the one I reported to firefox today or if it is a different problem.
-
Inappropriate?in about config you need to toggle : javascript.options.jit.content : to enable jit. -
Inappropriate?Mikael is correct about what you need to do in order to turn on tracemonkey. It is not automatically on in 3.1, I suspect it is alpha.
I can't replicate the problem since it came from the upgrade to 1.2.55. Once the upgrade loaded in 3.0 it was also uploaded in 3.1. In order to duplicate this problem I would need to:
1) uninstall feedly
2) install the previous version of feedly
3) open firefox 3.1 and let it try to download 1.2.55 again.
Unfortunately, I don't have time today to try this out for you. I might be able to do this during the weekend.
Michael -
Inappropriate?ps. In regard to the size of my 'friends', I don't really follow anyone. I added 22 friends from some getting started page you had posted; however, I never really visit that tab. If it helps you guage the total size of my feedly, I've attached a screenshot of my dashboard.
However, I don't think this is the new problem. The problem I originally posted at the top of this thread occurred when I opened feedly, and therefore it might be related to the size of the thread downloaded.
This subsequent problem occurs when I open FF (not feedly) and feedly tries to upgrade itself to 1.2.55. At this time I haven't tried to open feedly, so it shouldn't have tried to download any feeds. Its just the action of FF downloading and upgrading feedly (I assume).
-
Inappropriate?Mikael. Thanks. I turned it on.
Michael. No need to waste your time reproducing this. If you happen to run into the problem. Just update this thread if you see the crash happen again with the feedly version and if you have it the mozilla crash report.
Thanks!! -
Inappropriate?Ok. Thank. We will keep an eye open. FYI. both problems might be related because right after feedly patches itself (the patch is only 250K), it will activate the recommendation engine which streams the recommendations from your friends and your friends' friends. This happens in a low priority background thread. In might case, the crash was happening because the index of the recommendations stream was very large when uncompressed and the native JSON parser in firefox was not able to process it and crashed instead.
Anyway. This is obvisouly important for us and we are going to track it down with the mozilla and have put a fix in 1.2.56 to avoid it so if you still see a crash post 1.2.56 it means that there is another problem.
Thanks again for your time. Much appreciated.
EMPLOYEE
