http://bugs.winehq.org/show_bug.cgi?id=15206
--- Comment #5 from Dan Kegel dank@kegel.com 2008-09-09 17:50:58 --- Bug came right back, still overflowed the twice as big arena. Changed it to 1MB instead of 64K. Now it's been running for ten minutes trying to work its way past 150K+ lines of the sort fixme:dbghelp_msc:codeview_snarf Unsupported symbol id 1012 at 99% cpu. Guess I'm hitting quadratic behavior? The .pdb files I'm using are built from scratch here and are twice as big as the ones on the nightly builder.
oprofile says:
samples % image name app name symbol name ------------------------------------------------------------------------------- 28077516 61.2073 dbghelp.dll.so dbghelp.dll.so enum_modW64_64 28077516 100.000 dbghelp.dll.so dbghelp.dll.so enum_modW64_64 [self] ------------------------------------------------------------------------------- 8256676 17.9991 dbghelp.dll.so dbghelp.dll.so module_new 8256676 100.000 dbghelp.dll.so dbghelp.dll.so module_new [self] ------------------------------------------------------------------------------- 1341044 2.9234 no-vmlinux no-vmlinux (no symbols) 1341044 100.000 no-vmlinux no-vmlinux (no symbols) [self]
Not sure I trust oprofile on wine yet, but I guess there's a chance this is telling us where the .pdb loading bottleneck is...?
winedbg is at 15 minutes of cpu time, no backtrace yet, no end in sight...