Opened 5 years ago

Last modified 18 months ago

#15569 closed bug

System freeze when attempting to execute large binary not loaded to disk cache — at Version 1

Reported by: X512 Owned by: nobody
Priority: normal Milestone: R1/beta5
Component: Drivers/Disk/USB Version: R1/Development
Keywords: Cc: pulkomandy, mmlr
Blocked By: Blocking:
Platform: All

Description (last modified by X512)

This is hrev53639 x86_64.

System has 8GB of RAM and page file is disabled.

When attempting to run blender directly after boot, executable loading stops at loading executable image and trying to open new windows or context menus cause permanent freeze of window thread. Systems become almost uncontrollable, normal shutdown process is not working.

strace:

~/Blender> strace -l blender -p 10 10 800 600
[  1393] create_area("rld heap", 0x7f364467c978, 0x6, 0x10000, 0x0, 0x3) = 0x39de (3 us)
[  1393] create_area("_rld_debug_", 0x7f364467c9a8, 0x6, 0x1000, 0x0, 0x103) = 0x39df (5 us)
[  1393] open(0xffffffff, "./blender", 0x0, 0x0) = 0x3 (4 us)
[  1393] normalize_path("/boot/home/Blender/blender", true, 0x7f364467b510) = 0x0 No error (9 us)
[  1393] read(0x3, 0x0, 0x7f364467b4d0, 0x40) = 0x40 (3 us)
[  1393] read(0x3, 0x40, 0x7f364467b910, 0xe0) = 0xe0 (1 us)
[  1393] reserve_address_range([0x293a648000], 0x7, 0x402c000) = 0x0 No error (1 us)
[  1393] map_file("blender_seg0ro", 0x7f364467b3e8, 0x1, 0x2f5e000, 0x1003, 0x1, true, 0x0, 0x7f8276c008) = 0x39e0 (125 us)

But after cat blender > /dev/null is executed, blender runs normally.

Change History (2)

comment:1 by X512, 5 years ago

Description: modified (diff)

by X512, 5 years ago

Attachment: CIMG4588.JPG added

Stack trace of blender thread after freeze.

Note: See TracTickets for help on using tickets.