Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

My windows app which spawns a process to run FF with a given URL gets a FF crash after five minutes or so with v42 but worked great in 41.02.

  • 1 Mbohovái
  • 1 oguereko ko apañuái
  • 2 Hecha
  • Mbohovái ipaháva FredMcD

dcastles
dcastles
more options

After Firefox is started as a separate process from within my dotNet app, I change the parent of the FF window using the WinAPI so that it is a child of a form in my app. This has worked great for over a year running FF 41.02 but when v42 was installed problems started occurring after about 5 minutes of running FF. Each FF process is started with a dedicated copy of a barebones profile created by the FF profile manager in v41.02. It seems like some asynchronous service or activity in FF is jumping in after about 5 minutes and causing the crash. Any help or thoughts would be appreciated regarding changes to v42 that might explain this new problem.

After Firefox is started as a separate process from within my dotNet app, I change the parent of the FF window using the WinAPI so that it is a child of a form in my app. This has worked great for over a year running FF 41.02 but when v42 was installed problems started occurring after about 5 minutes of running FF. Each FF process is started with a dedicated copy of a barebones profile created by the FF profile manager in v41.02. It seems like some asynchronous service or activity in FF is jumping in after about 5 minutes and causing the crash. Any help or thoughts would be appreciated regarding changes to v42 that might explain this new problem.

Opaite Mbohovái (1)

FredMcD
FredMcD
more options

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it and select Submit.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

aboutcrashesFx29