Lucy said
I'm not sure what info would be helpful to add to the article as I don't have any specific bug to point to, nor a workaround, and we don't want end users using nightlies.
I am thinking something like troubleshooting advice being modified according to user group.
Articles about say High Memory use or crashes could be written with graded troubleshooting advice, for an aurora user trying a nightly may be an option.
Some KB articles (including the Firefox uses too much memory or CPU resources - How to fix KB being discussed) have been based on Mozillazine articles, why not link sections directly to such articles or MDN blogs or docs, it would be inline with the policy of reducing the number of KB articles. Sections linked out do not produce an overhead in localization updates.
An example of the sort of thing you could write
* Consider another version of Firefox developers are continually improving Firefox as explained above, but sometimes there are unexpected side effects of any change, that affect a minority of users
**{for fx >=R } if your memory problem is apparently only in the latest version, you could temporarily revert to Firefox n-1 as explained in installing a previous version of firefox
** {for fx=R } as a user of Firefox n you could consider trying Firefox n+1Beta, the many improvements in that may help your memory problem you can switch between versions with the Firefox Button
**{for fx>>R} as an advanced user, you may be interested in using the more advanced features like about:memory in helping to track down your problem ... [could link to a blog for instance, or a locked? contributors thread with a list of current blogs or threads]
''Lucy [[#post-36591|said]]''
<blockquote>
I'm not sure what info would be helpful to add to the article as I don't have any specific bug to point to, nor a workaround, and we don't want end users using nightlies.
</blockquote>
I am thinking something like troubleshooting advice being modified according to user group.
Articles about say High Memory use or crashes could be written with graded troubleshooting advice, for an aurora user trying a nightly may be an option.
Some KB articles (including the [[High memory usage]] KB being discussed) have been based on Mozillazine articles, why not link sections directly to such articles or MDN blogs or docs, it would be inline with the policy of reducing the number of KB articles. Sections linked out do not produce an overhead in localization updates.
An example of the sort of thing you could write
* '''''Consider another version of Firefox''''' developers are continually improving Firefox as explained above, but sometimes there are unexpected side effects of any change, that affect a minority of users
**''{for fx >=R }'' if your memory problem is apparently only in the latest version, you could temporarily revert to Firefox n-1 as explained in [[installing a previous version of firefox]]
** ''{for fx=R }'' as a user of Firefox n you could consider trying Firefox n+1Beta, the many improvements in that may help your memory problem you can switch between versions with the [https://support.mozilla.com/en-US/kb/how-do-i-switch-update-channels#os=win&browser=fx4 Firefox Button]
**''{for fx>>R}'' as an advanced user, you may be interested in using the more advanced features like [http://kb.mozillazine.org/About_protocol_links about]:[http://blog.mozilla.com/nnethercote/2011/05/23/a-better-aboutmemory-stage-1-75/ memory] in helping to track down your problem ... [could link to a blog for instance, or a locked? contributors [/forums/knowledge-base-articles/706489 thread] with a list of current blogs or threads]