View Single Post
Old 06-18-2015, 10:38 AM   #126
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 1,006
Karma: 2003162
Join Date: Jun 2011
Device: PC, t1, t2, t3, Clara BW, Clara HD, Libra 2, Libra Color, Nxtpaper 11
Quote:
Originally Posted by Katsunami View Post
Would it be helpful to have a procmon log of a system that does -not- have this problem? I'm willing to make one, if desired.
I would say, it is more interesting to have one which has a 100% real freeze reproducible score, like HarryT, and compare that with a machine that never has one.

ProcMon must be configured to use the default filtering so *everything* is captured.
Scenario:
  1. Start ProcMon
  2. Confirm default filtering
  3. Start capturing
  4. Start calibre
  5. Wait till calibre ready
  6. Stop calibre
  7. Stop capturing ProcMon
  8. Save log in default ProcMon monitoring format
By comparing the logs side-by-side differences could be found (I hope )
(Inspected calibre versions / OS versions must be rather identical qua version and bit version, and plugins)

Last edited by DrChiper; 06-18-2015 at 10:49 AM. Reason: added plugins
DrChiper is offline   Reply With Quote